How do I install the Status skill?

Run npx skillmds@latest add harshanandak/status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Status safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Status?

harshanandak (@harshanandak) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Status by harshanandak — Agent Skill

Name: Status
Author: harshanandak

Status

Report where the project stands and what work is in flight -- the Forge status snapshot. Reach for this at session start or whenever the user says "/status", "where am I", "what's in progress", "catch me up", "resume work", or "what changed recently". It surfaces the workflow stage, your active/claimed issues, all issues ranked by composite score with conflict-risk flags, stale already-merged issues (which it closes), and recent commits. Use it to ORIENT and decide the next move -- it reports state; it does not plan, develop, or claim issues. Not for: routing to a stage skill or documenting the full issue-verb surface (kernel); ranking and EXPLAINING a single next-ready or blocked issue to hand off (triage-ready); everyday create/update/list/close/comment/search issue ops (issue-basics); the Hermes harness's token-bounded orient/recap contract (hermes-forge); or the post-merge CI health check that closes issues after a merge lands (verify).

harshanandak 8d8d7df 3 files · 6.1 KB Updated Sep 17, 2026

File contents

Check where you are in the project and what work is in progress.

Status Check

This skill helps you understand the current state of the project before starting new work.

Usage

/status

What This Skill Does

Step 0: Sync team state

# Sync team state before showing status
forge sync || true

Step 1: Smart Status (ranked issues with conflict detection)

bash scripts/smart-status.sh

This command dynamically computes and displays all issues ranked by composite score (priority, dependency impact, type, staleness, epic proximity). Output includes active sessions, conflict risk annotations, and grouped categories. No manual querying needed.

For full context on any issue: forge show <id>

For the full workflow contract and command reference at session start, run forge prime.

Step 1b: Reconcile stale in-progress issues

Check if any in-progress issues were already merged but not closed (can happen if /verify was skipped or backup was restored from stale snapshot):

# Detect default branch dynamically (prefer main over master)
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||')
if [ -z "$DEFAULT_BRANCH" ]; then
  if git rev-parse --verify main >/dev/null 2>&1; then DEFAULT_BRANCH="main"
  elif git rev-parse --verify master >/dev/null 2>&1; then DEFAULT_BRANCH="master"
  else echo "ERROR: No main or master branch found -- skipping stale reconciliation" >&2; DEFAULT_BRANCH=""; fi
fi

# For each in_progress issue, check if its PR was already merged
if [ -n "$DEFAULT_BRANCH" ]; then
  forge list --status=in_progress --json 2>/dev/null | jq -r '.[].id' | while read id; do
    # Search git log for the issue ID in commit messages (fixed-strings for literal match)
    if git log --oneline --first-parent "$DEFAULT_BRANCH" --fixed-strings --grep="$id" | grep -q .; then
      echo "STALE: $id -- found in git history, likely already merged"
    fi
  done
fi

If stale issues are found, close them:

forge close <id> --force --reason="Already merged -- detected during status reconciliation"

Step 2: Review Recent Commits

git log --oneline -10

Step 3: Determine Context

New feature: No active work, ready to start fresh
Continuing work: In-progress issues found, resume where left off
Review needed: Work marked complete, needs review/merge

Team context

Show current developer's active work and team overview:

# Show my active issues
forge team workload --me 2>&1 || true

# One-line team summary
forge team dashboard 2>&1 | head -5 || true

Next Steps

If starting new work: Run /plan <feature-name>
If continuing work: Resume with appropriate phase command
If reviewing: Run /review <pr-number> (the pre-merge doc gate is embedded in /ship and /review)

---name: statusdescription: Report where the project stands and what work is in flight -- the Forge status snapshot. Reach for this at session start or whenever the user says "/status", "where am I", "what's in progress", "catch me up", "resume work", or "what changed recently". It surfaces the workflow stage, your active/claimed issues, all issues ranked by composite score with conflict-risk flags, stale already-merged issues (which it closes), and recent commits. Use it to ORIENT and decide the next move -- it reports state; it does not plan, develop, or claim issues. Not for: routing to a stage skill or documenting the full issue-verb surface (kernel); ranking and EXPLAINING a single next-ready or blocked issue to hand off (triage-ready); everyday create/update/list/close/comment/search issue ops (issue-basics); the Hermes harness's token-bounded orient/recap contract (hermes-forge); or the post-merge CI health check that closes issues after a merge lands (verify).---Check where you are in the project and what work is in progress.# Status CheckThis skill helps you understand the current state of the project before starting new work.## Usage```bash/status```## What This Skill Does## Step 0: Sync team state```bash# Sync team state before showing statusforge sync || true```### Step 1: Smart Status (ranked issues with conflict detection)```bashbash scripts/smart-status.sh```This command dynamically computes and displays all issues ranked by composite score (priority, dependency impact, type, staleness, epic proximity). Output includes active sessions, conflict risk annotations, and grouped categories. No manual querying needed.For full context on any issue: `forge show <id>`For the full workflow contract and command reference at session start, run `forge prime`.### Step 1b: Reconcile stale in-progress issuesCheck if any in-progress issues were already merged but not closed (can happen if `/verify` was skipped or backup was restored from stale snapshot):```bash# Detect default branch dynamically (prefer main over master)DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||')if [ -z "$DEFAULT_BRANCH" ]; then if git rev-parse --verify main >/dev/null 2>&1; then DEFAULT_BRANCH="main" elif git rev-parse --verify master >/dev/null 2>&1; then DEFAULT_BRANCH="master" else echo "ERROR: No main or master branch found -- skipping stale reconciliation" >&2; DEFAULT_BRANCH=""; fifi# For each in_progress issue, check if its PR was already mergedif [ -n "$DEFAULT_BRANCH" ]; then forge list --status=in_progress --json 2>/dev/null | jq -r '.[].id' | while read id; do # Search git log for the issue ID in commit messages (fixed-strings for literal match) if git log --oneline --first-parent "$DEFAULT_BRANCH" --fixed-strings --grep="$id" | grep -q .; then echo "STALE: $id -- found in git history, likely already merged" fi donefi```If stale issues are found, close them:```bashforge close <id> --force --reason="Already merged -- detected during status reconciliation"```### Step 2: Review Recent Commits```bashgit log --oneline -10```### Step 3: Determine Context- **New feature**: No active work, ready to start fresh- **Continuing work**: In-progress issues found, resume where left off- **Review needed**: Work marked complete, needs review/merge### Team contextShow current developer's active work and team overview:```bash# Show my active issuesforge team workload --me 2>&1 || true# One-line team summaryforge team dashboard 2>&1 | head -5 || true```## Next Steps- **If starting new work**: Run `/plan <feature-name>`- **If continuing work**: Resume with appropriate phase command- **If reviewing**: Run `/review <pr-number>` (the pre-merge doc gate is embedded in `/ship` and `/review`)

Frequently asked questions