forge
Installation
SKILL.md
Forge
Forge an issue into a shipped fix: heat it (implement), hammer it (review loop), then temper it (refactor).
Overview
Turn an issue or ticket reference into a verified, branch-correct, user-approved plan. Then, only after the user confirms (or immediately under automode), run the implementation lifecycle.
One numbered workflow (Steps 1–12), split by a single gate:
Part 1 — Gate (Steps 1–6): classify → fetch → branch → context → propose → [GATE] approve
Part 2 — Lifecycle (7–12): implement → review-loop → refactor → spin-off → self-evolve → close
gate held: nothing touches the codebase until "yes, implement" (automode = only sanctioned bypass)
- Part 1 — The gate. The contract; do not weaken it.
- Part 2 — Lifecycle. Runs autonomously after approval, stopping only at substantive gates (the Autonomy section).