backprop
CommandTrace a bug back to a spec gap and generate regression tests
Audit every skill and command Forge can see — group by status (active, duplicate, deprecated, archived)
> /plugin marketplace add LucasDuys/forge> /plugin install forge@forge-marketplace
description: "Audit every skill and command Forge can see — group by status (active, duplicate, deprecated, archived)"
allowed-tools: ["Read(*)", "Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/forge-skills-audit.cjs:*)"]List every skill and slash-command visible to the current Forge install, with source + path + status. Output is designed to be copy-paste-ready into a "skills cleanup" PR description.
Invoke the inventory script. Default output is a fixed-width table; pass `--json` for machine-readable output.
node "${CLAUDE_PLUGIN_ROOT}/scripts/forge-skills-audit.cjs"The script walks:
`archived` when the path sits under `_archived-*/` or `archived/`).
plugin-shipped skill (source `plugin:<plugin>`).
plugin-shipped command.
| Status | Meaning | |------------|---------| | active | Healthy, loadable, not flagged. | | duplicate | Same name appears in ≥ 2 sources (e.g. `user-skills` and a plugin, or two plugins). Resolve by deleting the stale copy. | | deprecated | SKILL.md description starts with `Deprecated`. The skill loader may still pick it up; prefer the replacement noted in the description. | | archived | Path contains `_archived-*/` or `archived/`. Kept for reference; should not be invoked. |
Render the table output verbatim under a `### Skills Audit (<date>)` heading in the PR description. Follow it with the summary line the script prints (`totals: ...` + `status: ...`). Call out any `duplicate` rows as action items for the cleanup PR.
If a user asks for JSON (or wants to pipe the output into another tool), run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/forge-skills-audit.cjs" --jsoncorrupt `plugin.json` or `SKILL.md` that broke the underlying `discoverCapabilities` walk. Surface the error to the user; do not try to "fix" the skill file from this command.
machine (e.g. running inside an ephemeral sandbox). Let the user know.
Turn a one-line idea into a branch with tested, reviewed, committed code. The brainstorm-to-commit pipeline for Claude Code.
Trace a bug back to a spec gap and generate regression tests
Turn an idea into concrete specs with testable requirements
Opt-in multiplayer mode -- brain-dump together, claim tasks across machines, flag decisions async
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.