skills/forge-recover/SKILL.md
[writes] Diagnose or fix pipeline state — read-only diagnose (default), repair counters/locks, reset clearing state while preserving caches, resume from checkpoint, rollback worktree commits, rewind to any prior checkpoint (time-travel), or list the checkpoint DAG. Use when pipeline stuck, failed with state errors, or you need to explore alternate execution paths. Trigger: /forge-recover, diagnose state, repair pipeline, reset state, resume from checkpoint, rollback commits, rewind checkpoint, time travel, list checkpoints
npx skillsauth add quantumbitcz/dev-pipeline forge-recoverInstall 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.
Single entry point for pipeline state recovery. Replaces /forge-diagnose, /forge-repair-state, /forge-reset, /forge-resume, /forge-rollback (all removed in 3.0.0).
| Subcommand | Read/Write | Purpose |
|---|---|---|
| diagnose (default) | read-only | Health check of state.json, recovery budget, convergence, stalled stages |
| repair | writes | Fix counters, stale locks, invalid stages, WAL recovery |
| reset | writes | Clear pipeline state (preserves cross-run caches) |
| resume | writes | Resume from last checkpoint |
| rollback | writes | Revert pipeline commits in worktree |
| rewind --to=<id> [--force] | writes | Time-travel to any checkpoint. Atomic four-tuple restore (state, worktree, events, memory). Aborts on dirty worktree unless --force. |
| list-checkpoints [--json] | read-only | Render the checkpoint DAG with current HEAD marked. |
PLAN.-.003) or sha256. Required.| Code | Meaning |
|---|---|
| 0 | success |
| 1 | generic failure |
| 2 | usage error (missing --to, etc.) |
| 5 | rewind aborted: dirty worktree (use --force to override) |
| 6 | rewind aborted: unknown checkpoint id |
| 7 | rewind aborted: another rewind transaction in progress |
See shared/skill-contract.md for the standard exit-code table.
.forge/state.json exists (for diagnose, resume, repair, rollback subcommands)rollback)Dispatch fg-100-orchestrator with recovery_op set to the subcommand name. See agents/fg-100-orchestrator.md §Recovery op dispatch for routing details. The orchestrator reads the current .forge/state.json, routes to the appropriate recovery strategy (per shared/recovery/recovery-engine.md), and applies the operation atomically via shared/forge-state-write.sh.
Exit codes per shared/skill-contract.md:
/forge-abort -- Stop an active pipeline run before attempting recovery/forge-status -- Check pipeline state to decide which recovery subcommand to use/forge-history -- Review prior run outcomes when planning a rollbackshared/skill-contract.md — standard exit codes and flag conventionsshared/state-schema.md — state.json schema and recovery fieldsagents/fg-100-orchestrator.md — recovery dispatch routing/forge-recover # diagnose (read-only default)
/forge-recover diagnose --json # JSON output for scripting
/forge-recover repair --dry-run # preview repairs
/forge-recover reset # prompts confirmation via AskUserQuestion
/forge-recover resume # continue from last checkpoint
/forge-recover rollback --target main # revert main branch
/forge-recover list-checkpoints # show DAG with HEAD marked
/forge-recover list-checkpoints --json # machine-readable
/forge-recover rewind --to=PLAN.-.003 # time-travel restore
/forge-recover rewind --to=a3f9c1 --force # override dirty worktree guard
Dispatches fg-100-orchestrator with recovery_op: diagnose|repair|reset|resume|rollback|rewind|list-checkpoints on its input payload. See agents/fg-100-orchestrator.md §Recovery op dispatch and shared/state-schema.md for the payload schema. Rewind and list-checkpoints are backed by hooks/_py/time_travel/ (invoked as python3 -m hooks._py.time_travel; see shared/recovery/time-travel.md).
Replacements for removed skills:
| Old skill | New invocation | |---|---| | /forge-diagnose | /forge-recover diagnose | | /forge-repair-state | /forge-recover repair | | /forge-reset | /forge-recover reset | | /forge-resume | /forge-recover resume | | /forge-rollback | /forge-recover rollback |
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.