code-forge

Use when encountering any bug, test failure, or unexpected behavior — enforces root cause investigation before fixes

Use when implementation is complete and you need to merge, create a PR, or clean up — guides branch integration with 4 structured options

Use when fixing a bug in a code-forge tracked feature (has state.json) — traces root cause across 4 levels and syncs upstream plan/task documents

Show all code-forge commands and usage guide

Use when implementing a feature — executes TDD tasks via sub-agents with state tracking and auto-resume

Use when facing 2+ independent problems that can be solved concurrently — dispatches one agent per problem domain

Use when creating an implementation plan from docs or requirements — generates TDD tasks with progress tracking

Use when porting a project to another language — batch-generates plans for all features in the target language

Use when reviewing code, handling review feedback, or posting a review to a GitHub PR — 14-dimension quality analysis, structured feedback response, or automated PR review comment

Use when checking implementation progress — shows feature dashboard with task completion and next steps

Use when implementing any feature or fix outside code-forge workflow — enforces Red-Green-Refactor cycle with mandatory test-first discipline

Use before claiming work is done, fixed, or passing — requires running verification commands and confirming output before any success claim

Use when starting feature work that needs workspace isolation — creates git worktree with project setup and baseline tests

Use when encountering any bug, test failure, or unexpected behavior — enforces root cause investigation before fixes. Prevents symptom-fixing, masking bugs, and "just try this" approaches. For code-forge features, use code-forge:fixbug instead.

Use when implementation is complete and you need to merge, create a PR, or clean up — verifies tests pass, presents 4 structured integration options, executes chosen workflow, and cleans up worktrees. Pairs with code-forge:worktree.

Debug and fix bugs with interactive upstream trace-back — diagnoses root cause level, confirms upstream document updates, and applies TDD fixes.

Execute pending tasks for a feature — TDD-driven implementation with sub-agent isolation and progress tracking.

Use when facing 2+ independent problems that can be solved concurrently — dispatches one sub-agent per problem domain for parallel investigation and fixing. For parallel task execution within a feature, use code-forge:impl instead.

Analyze documentation (or a prompt) and generate an implementation plan with task breakdown, TDD steps, and progress tracking.

Port a documentation-driven project to a new target language — initializes project skeleton, analyzes reference implementation, and batch-generates plans for selected features.

Use when reviewing code, handling review feedback, or posting a review to a GitHub PR — 14-dimension quality analysis for features or entire projects (generate mode), structured evaluation and response to incoming review comments (feedback mode via --feedback flag), or automated PR review posted as a GitHub comment (--github-pr flag).

Display feature dashboard, progress tracking, and project-level overview.

Use when implementing any feature or fix outside code-forge workflow — enforces Red-Green-Refactor cycle with mandatory test-first discipline. For ad-hoc development, quick fixes, or any code change that is not tracked by code-forge:impl.

Use before claiming work is done, fixed, or passing — requires running verification commands and confirming output before any success claim. Prevents false completion claims, unverified assertions, and "should work" statements.

Use when starting feature work that needs workspace isolation — creates git worktree with automatic project setup and baseline test verification. Ensures worktree directory is git-ignored and safe. Integrates with code-forge:impl and code-forge:finish.