forge

Activates when reviewing a Forge-launched pull request. Reads the PR diff, compares it against the original Forge spec when one is available, and produces a structured review verdict the user (or downstream automation) can act on. Use when the user asks to review, score, or check whether a Forge PR is mergeable.

Activates when an operator selects review items (Forge findings, inline comments, and/or review summaries) in the Forge review UI and clicks 'Fix N selected'. Validates each selected target against the current code, then surgically fixes only the targets judged valid. Used by the forge __comment-fix-worker pipeline.

Activates when the user wants to turn an idea or a plan-mode plan into a Forge task spec — research the repo, draft in the Forge schema, then persist via `forge spec save`. Use when the user says they want to run something with Forge, when they've just produced a plan they want to ship to a coding agent, or when they explicitly invoke /forge-ship-plan.

Applies a curated subset of synthesizer recommendations to a Forge spec body. Invoked programmatically by the auto-improve orchestrator after `forge spec save`; not auto-activated.

Adversarial critique of a Forge task spec. Identifies vague acceptance criteria, undefined behavior, contradictions, missing edge cases, scope creep, and assumptions deferred to the implementing agent. Produces a structured findings list with severity labels.

Activates during the forge auto-fix loop after a reviewer returns request-changes. Reads the review findings, reads the spec, and surgically fixes BLOCKER and HIGH severity issues only. Used by the forge runner after a reviewer verdict of request-changes.

Synthesizes two independent spec critiques into a single prioritized recommendations document. Classifies findings as corroborated, single-critic-only, or conflicting, and proposes concrete spec edits the user can selectively apply.