flow

Address PR review feedback systematically. Categorizes feedback, implements surgical fixes, verifies changes, and re-requests review.

Explore approaches before committing to implementation. Generates options, analyzes trade-offs, and helps select the best approach collaboratively.

Classify changes and create atomic commits with conventional messages. Flags out-of-context modifications and red-flag patterns before committing.

Debug an issue with structured root cause analysis. Guides evidence gathering, hypothesis testing, and fix validation.

Design or review architecture for a feature or system. Analyzes existing patterns, evaluates coupling, and produces design decisions.

Review code changes for quality, logic correctness, edge cases, security, and error handling. Return P1/P2/P3 findings with file:line citations using the ASSERTION/EVIDENCE/VERIFIED pattern.

Validate Git conventions including commit messages, branch naming, PR format, and code patterns. Report convention violations with severity.

Inspect code for unhandled errors, missing edge cases, silent failures, and exception handling gaps. Return P1/P2/P3 findings with file:line citations.

Parse acceptance criteria from issues and create task breakdowns with dependencies and parallel execution opportunities. Use when decomposing an issue into trackable implementation tasks.

Verify end-to-end functionality beyond unit tests. Start dev servers, run E2E suites, perform smoke tests, and validate acceptance criteria at runtime.

Guide system design decisions including design-from-functionality, coupling analysis, and C4 model thinking. Use when designing systems, evaluating structural changes, or reviewing architecture decisions.

Govern autonomous development execution through the Explore-Plan-Code-Verify loop, task-driven progress tracking, three-tier action classification, decision journaling, and bounded verification. Use when executing any development workflow autonomously or orchestrating multi-step implementation tasks.

Explore multiple approaches through structured option generation, trade-off analysis, and collaborative approach selection. Use when evaluating alternatives before committing to an implementation strategy.

Create branches with naming conventions, load issue context, perform impact analysis, and decompose acceptance criteria into parallel tasks. Use when starting work on a GitHub issue.

Discover available agents, skills, quality commands (lint, test, typecheck), tech stack, and LSP code intelligence capabilities in the project environment. Use when starting implementation, creating PRs, reviewing PRs, or addressing feedback to determine which agents to dispatch and which quality commands to run.

8 hooks across 5 events