agentleFS
akshaypimprikarakshaypimprikar/pragma/.claude/skills/status/SKILL.md

status

Skill4 starsChanged 5 days agoMITView on GitHub

Reconstruct where work stands in the pipeline so any session can resume without guessing. Invoke at the start of a session or after a gap between sessions.

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 157 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run at the start of any session to orient yourself, or after any gap between sessions: /status

    line 12
  2. Distinctive:

    Run these commands in order, then synthesise the report below.

    line 16
  3. Very specific:

    Read the most recently modified plan file.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 157 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Status Agent

You are the Status Agent for an iOS app project. Your job is to reconstruct where work stands in the pipeline so any session can resume without guessing.

Trigger

Run at the start of any session to orient yourself, or after any gap between sessions: /status

Process

Run these commands in order, then synthesise the report below.

1. Current branch and phase

git branch --show-current

Map branch prefix → pipeline phase:

Branch prefixPhase
feature/*/feature — implementation in progress
fix/*/bugfix — bug fix in progress
spec/*/spec — specification in progress
design/*/design — design tokens in progress
release/*/release — release in progress
hotfix/*/bugfix (hotfix) — fix off main, PRs to both main and develop
chore/*Maintenance (pipeline, docs, settings)
ci/*Pipeline/infrastructure work
develop or mainNo active feature branch

2. Commits on branch vs develop

git log develop..HEAD --oneline 2>/dev/null || git log --oneline -10

3. Open PRs

gh pr list --state open --json number,title,baseRefName --jq '.[] | "#\(.number) \(.title) → \(.baseRefName)"'

4. Plan document (feature branches only)

ls -t docs/superpowers/plans/*.md 2>/dev/null | head -3

Read the most recently modified plan file. Count lines starting with ## Task to get total task count. Compare against commit count on branch to estimate remaining tasks.

5. CHANGELOG status

awk '/^## \[Unreleased\]/{f=1; next} /^## /{f=0} f && /^-/{n++} END{print n+0}' CHANGELOG.md 2>/dev/null || echo 0

6. Unaddressed pipeline reviews

for f in docs/pipeline-review/*.md; do [ -f "$f" ] && awk 'NR==1 && !/^---/{exit} NR>1 && /^---/{exit} /^addressed:[[:space:]]*"?false"?[[:space:]]*(#.*)?$/{print FILENAME; exit}' "$f"; done 2>/dev/null | wc -l | tr -d ' '

7. Last activity

git log -1 --format="%s (%cr)"

Output format

Print this block — fill in each field from the commands above:

══════════════════════════════════════
  <AppName> — Pipeline Status
══════════════════════════════════════
Branch:       <branch name>
Phase:        <phase from table above>
Last commit:  <subject> (<relative time>)
Branch ahead: <N> commit(s) since develop

Plan:         <plan file path, or "none found">
Tasks:        <N committed> of <M total> (estimated)

Open PRs:     <list, or "none">
CHANGELOG:    <N Unreleased entries, or "⚠ none — update before /gates">
Reviews:      <N unaddressed findings, or "✓ none">

Next action:  <one-line recommendation — see table below>
══════════════════════════════════════

Next action logic:

SituationRecommended next action
On feature branch, no PR open, tasks remainingContinue /feature from task N
On feature branch, no PR open, all tasks committedRun /gates then open PR
On feature branch, PR openRun /review on PR #N
On develop, pipeline review unaddressedAddress docs/pipeline-review/<file> before new work
On develop, no unaddressed reviewsStart new work with /spec
On release branchContinue /release

Done when

Status report delivered. No commits, no file changes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.