agentleFS
Sign inStart free
lionshilovlionshilov/Forge/.claude/skills/forge-status/SKILL.md

forge-status

Skill5 starsChanged 34 days agoMITView on GitHub

Show current Forge project state — phase gates, task board, recent failures, blockers — and recommend the next action per the routing rules.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    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 bash .claude/hooks/forge-gate.sh status — the phase-gate board (which context files are template / draft / ready, and which agents each …

    line 8
  2. Very specific:

    Read project_context/PROGRESS.md and project_context/ERRORS_LOG.md (last 5 entries max) where the board isn't enough.

    line 9
  3. Distinctive:

    Run git log --oneline -10 and git status --short for ground truth on what actually changed.

    line 10
  4. Distinctive:

    Do not start executing the next action — report and wait for the user.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 8 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

You are the Forge Orchestrator. Produce a status report:

  1. Run bash .claude/hooks/forge-gate.sh status — the phase-gate board (which context files are template / draft / ready, and which agents each closed gate blocks), open tasks, latest errors.
  2. Read project_context/PROGRESS.md and project_context/ERRORS_LOG.md (last 5 entries max) where the board isn't enough.
  3. Run git log --oneline -10 and git status --short for ground truth on what actually changed.
  4. Cross-check: tasks marked 🟢 Done should have corresponding commits/files, and a context file marked ready should hold real decisions, not template placeholders. Flag mismatches — a board that lies is worse than no board.

Report back:

  • Gates — which are closed and what each one blocks
  • Done / In progress / Blocked — one line per task, straight from the table
  • Failures worth attention — repeated ERR- entries or tasks approaching the 3-retry escalation limit
  • Next action — the single highest-leverage next step per the Routing Rules in root CLAUDE.md; usually opening the closed gate that blocks queued work (e.g. "DESIGN.md is template but a UI task is queued → dispatch Designer first")

Do not start executing the next action — report and wait for the user.

Download now (ZIP)

  • Other versions11 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 11

    1. TT-Wang/forge★ 34same name
    2. ggombee/code-forge★ 18same name
    3. lorenzofamiglini/The-Forge-Protocol-Agent★ 15same name
    4. antonailog/forge-skills★ 13same name
    5. yike-gunshi/forge-skills★ 13same name
    6. coreweave/forge-agent-lens-for-claude-code★ 9same name
    7. wandb/forge-agent-lens-for-claude-code★ 9same name
    8. wandb/forge-claude-code★ 9same name
    9. wandb/weave-claude-code★ 9same name
    10. tonmoy007/forge-plugins★ 2same name

    1 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use forge-config, forge-install and 1 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.
    • coreweaveSkill

      forge-config

      This skill should be used when the user wants to "configure Forge", "set Forge project", "change Forge project", "set wandb api key", "update Forge settings", "show Forge config", "change Forge configuration", "restart the Forge daemon", "apply Forge config changes", "restart Forge to pick up changes", or needs to read or update any Forge Agent Lens for Claude Code plugin settings.

      Also in 4 projects that use this

    • coreweaveSkill

      forge-install

      This skill should be used when the user wants to "install the Forge plugin", "set up Forge", "install forge-agent-lens-for-claude-code", "configure Forge for the first time", "get started with Forge tracing", or needs to complete the initial setup of the Forge Agent Lens for Claude Code plugin including dependency installation and project configuration.

      Also in 4 projects that use this

    • tonmoy007Skill

      forge-review

      Run a multi-dimensional parallel code review over the current change.

      Also in 3 projects that use this

  • In this repository6 other files it gives its agents.

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