agentleFS
Sign inStart free
amrtawfik160amrtawfik160/bb-orchestration-skills/skills/run-status/SKILL.md

run-status

Skill1 starsChanged 58 days agoMITView on GitHub

Print a one-pane status of a BB orchestration run from its ledger: tickets, PRs, checks, child threads, and blockers. Use when asked where a run stands.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Read the ledger, never write it.

    line 15
  2. Very specific:

    Read the ledger and map every field the format needs.

    line 31
  3. Distinctive:

    Stop. A stale or contradictory record is reported, never repaired.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Run Status

Answer "where does the run stand" from the ledger, the child threads, and the PRs. Read-only and single-turn: queue no continuation, spawn nothing, and write nothing.

Contract

  • Read the ledger, never write it. Spawning workers and mutating gh or git commands are out of scope; bb thread tell is never sent.
  • Resolve one ledger: the attached path, else $BB_THREAD_STORAGE/orchestrate-implementation/run.json, else $BB_THREAD_STORAGE/review-fix-loop/<base7>.json, else ask.
  • Report children with bb thread count and bb thread list, and PR checks with read-only gh pr checks and gh pr view. Take no action on what they show.
  • Render in references/format.md and stop.

References

references/format.md owns the output sections and field mapping.

Report

  1. Read the ledger and map every field the format needs; reconcile thread states with bb thread show and PR states with gh pr view before printing.
  2. Print the format's sections in order, with ledger path, thread IDs, and PR URLs as pointers. Name the pause, the quarantine, and the red-main response when one is present; a missing gate verdict is a finding.
  3. Stop. A stale or contradictory record is reported, never repaired.

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.

Check your setup, free