skills/forge-help/SKILL.md
[read-only] Interactive decision tree to find the right Forge skill. Use when unsure which skill to use, exploring capabilities, or need help choosing between similar skills. Trigger: /forge-help, which skill should I use, help me choose, what can forge do
npx skillsauth add quantumbitcz/dev-pipeline forge-helpInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
## --json output below; envelope carries schema_version)See shared/skill-contract.md for the standard exit-code table.
None. This skill is a reference guide.
Display the decision tree below. If the user asks a specific question, navigate to the relevant category. With --json, emit the structured envelope documented under ## --json output.
None. This skill displays static content.
What do you want to do?
├── Build something
│ ├── New feature ................. /forge-run
│ ├── Fix a bug ................... /forge-fix
│ ├── Refine a vague idea ......... /forge-shape
│ └── Scaffold a new project ...... /forge-bootstrap
│
├── Check quality
│ ├── Just my recent changes ...... /forge-review (default: --scope=changed --fix)
│ ├── The whole codebase (read) ... /forge-review --scope=all
│ ├── The whole codebase (fix) .... /forge-review --scope=all --fix
│ ├── Build + lint + test ......... /forge-verify (default: --build)
│ ├── Config is correct ........... /forge-verify --config
│ └── Security scan ............... /forge-security-audit
│
├── Work with the knowledge graph
│ └── /forge-graph <init|status|query|rebuild|debug>
│
├── Ship / deploy / commit
│ ├── Deploy ...................... /forge-deploy
│ └── Conventional commit ......... /forge-commit
│
├── Pipeline control
│ ├── Status ...................... /forge-status
│ ├── Abort ....................... /forge-abort
│ ├── Recover ..................... /forge-recover <diagnose|repair|reset|resume|rollback>
│ └── Profile a run ............... /forge-profile
│
├── Know the codebase / history
│ ├── Ask a question .............. /forge-ask
│ ├── Run history ................. /forge-history
│ └── Insights .................... /forge-insights
│
└── Configure / automate / compress
├── Edit config ................. /forge-config
├── Automations ................. /forge-automation
├── Playbooks (list) ............ /forge-playbooks
├── Playbooks (refine) .......... /forge-playbook-refine
├── Compress .................... /forge-compress <agents|output|status|help>
├── Docs generate ............... /forge-docs-generate
└── Migration ................... /forge-migration
New to forge? → /forge-tour
First setup? → /forge-init
Tree depth: maximum 3 levels (root → category → item). Subcommands live inside the skill, not as a 4th tree branch.
The following skill names were removed in the skill-consolidation pass. Use the replacement on the right:
| Removed | Use instead | |-------------------------|------------------------------------------| | /forge-codebase-health | /forge-review --scope=all | | /forge-deep-health | /forge-review --scope=all --fix | | /forge-graph-status | /forge-graph status | | /forge-graph-query | /forge-graph query <cypher> | | /forge-graph-rebuild | /forge-graph rebuild | | /forge-graph-debug | /forge-graph debug | | /forge-config-validate | /forge-verify --config |
This section is slated for removal in the release after the next minor bump.
/forge-tour — guided 5-stop introduction for new users/forge-init — first-time project setup/forge-compress help — compression features referenceWhen invoked with --json, /forge-help emits the decision tree as structured JSON. The envelope carries an explicit schema_version so downstream consumers (MCP server F30, /forge-insights) can detect the shape:
{
"schema_version": "2",
"total_skills": 29,
"categories": {
"build": [
{"name": "forge-run", "mode": "writes", "summary": "Full 10-stage pipeline"},
{"name": "forge-fix", "mode": "writes", "summary": "Root cause bug fix"},
{"name": "forge-shape", "mode": "writes", "summary": "Refine a vague idea"},
{"name": "forge-bootstrap", "mode": "writes", "summary": "Scaffold a new project"}
],
"quality": [
{
"name": "forge-review",
"mode": "writes",
"summary": "Quality review for changed files or whole codebase",
"subcommands": [
{"name": "changed", "mode": "writes", "default": true},
{"name": "all", "mode": "read-only"},
{"name": "all --fix", "mode": "writes"}
]
},
{
"name": "forge-verify",
"mode": "read-only",
"summary": "Pre-pipeline checks",
"subcommands": [
{"name": "build", "mode": "read-only", "default": true},
{"name": "config", "mode": "read-only"},
{"name": "all", "mode": "read-only"}
]
},
{"name": "forge-security-audit", "mode": "read-only", "summary": "Security scan"}
],
"knowledge_graph": [
{
"name": "forge-graph",
"mode": "writes",
"summary": "Neo4j knowledge graph (Docker)",
"subcommands": [
{"name": "init", "mode": "writes"},
{"name": "status", "mode": "read-only"},
{"name": "query", "mode": "read-only"},
{"name": "rebuild", "mode": "writes"},
{"name": "debug", "mode": "read-only"}
]
}
],
"ship": [
{"name": "forge-deploy", "mode": "writes", "summary": "Deploy to staging/production/preview"},
{"name": "forge-commit", "mode": "writes", "summary": "Generate conventional commit messages"}
],
"pipeline_control": [
{"name": "forge-status", "mode": "read-only", "summary": "Check pipeline state and progress"},
{"name": "forge-abort", "mode": "writes", "summary": "Stop active run, preserve for resume"},
{
"name": "forge-recover",
"mode": "writes",
"summary": "Unified recovery dispatcher",
"subcommands": [
{"name": "diagnose", "mode": "read-only"},
{"name": "repair", "mode": "writes"},
{"name": "reset", "mode": "writes"},
{"name": "resume", "mode": "writes"},
{"name": "rollback", "mode": "writes"}
]
},
{"name": "forge-profile", "mode": "read-only", "summary": "Per-stage / agent timing"}
],
"know": [
{"name": "forge-ask", "mode": "read-only", "summary": "Ask questions about the codebase"},
{"name": "forge-history", "mode": "read-only", "summary": "Score trends across runs"},
{"name": "forge-insights", "mode": "read-only", "summary": "Cross-run quality + cost analytics"}
],
"configure": [
{"name": "forge-config", "mode": "writes", "summary": "Edit pipeline settings interactively"},
{"name": "forge-automation", "mode": "writes", "summary": "Set up automatic pipeline triggers"},
{"name": "forge-playbooks", "mode": "read-only", "summary": "List/manage reusable pipeline recipes"},
{"name": "forge-playbook-refine", "mode": "writes", "summary": "Review/apply playbook refinement proposals"},
{
"name": "forge-compress",
"mode": "writes",
"summary": "Token compression dispatcher",
"subcommands": [
{"name": "agents", "mode": "writes"},
{"name": "output", "mode": "writes"},
{"name": "status", "mode": "read-only"},
{"name": "help", "mode": "read-only"}
]
},
{"name": "forge-docs-generate", "mode": "writes", "summary": "Generate README, ADRs, API specs"},
{"name": "forge-migration", "mode": "writes", "summary": "Framework / library version upgrade"}
]
},
"removed_in_phase_05": [
{"name": "forge-codebase-health", "replacement": "/forge-review --scope=all"},
{"name": "forge-deep-health", "replacement": "/forge-review --scope=all --fix"},
{"name": "forge-config-validate", "replacement": "/forge-verify --config"},
{"name": "forge-graph-status", "replacement": "/forge-graph status"},
{"name": "forge-graph-query", "replacement": "/forge-graph query <cypher>"},
{"name": "forge-graph-rebuild", "replacement": "/forge-graph rebuild"},
{"name": "forge-graph-debug", "replacement": "/forge-graph debug"}
]
}
Schema version history:
{ total_skills: 35, tiers: { essential, power_user, advanced }, similar_skills: [...] } — flat tier tables.{ schema_version, total_skills: 28, categories: {...}, removed_in_phase_05: [...] } — categorized with cluster entries carrying subcommands arrays.Consumers SHOULD switch on schema_version rather than sniffing for the presence of subcommands.
development
[writes] Build, fix, deploy, review, or modify code in this project. Universal entry for the forge pipeline. Auto-bootstraps on first run; brainstorms before planning when given a feature description. Use when you want to take any productive action: implementing features, fixing bugs, reviewing branches, deploying, committing, running migrations.
tools
[writes] Manage forge state and configuration: recovery, abort, config edits, session handoff, automations, playbooks, output compression, knowledge graph maintenance. Use when you need to recover from broken pipeline state, edit settings, or manage long-lived state.
development
[writes] Create, list, show, resume, or search forge session handoffs. Use when context is getting heavy and you want to transfer a forge run or conversation into a fresh Claude Code session, or to resume from a prior handoff artefact. Subcommands - no args (write), list, show, resume, search.
development
[writes] Manage the Neo4j knowledge graph. Subcommands: init, rebuild (writes); status, query <cypher>, debug (read-only). Requires Docker. No default — an explicit subcommand is required. Use when setting up the graph for the first time, rebuilding after major refactors, checking graph health, or running ad-hoc Cypher diagnostics.