code-review

Code Review

Stack-aware code review orchestrator. Detects the tech stack from changed files, validates companion skills, dispatches parallel review lanes, synthesizes findings, runs a fix loop, and optionally reflects.

How To Use This Skill

Run this skill on a feature branch with uncommitted or committed changes. The orchestrator will:

1. Validate that required companion skills are installed
2. Scope the review from git diff and git status
3. Detect stacks and route review lanes
4. Dispatch parallel subagents with prescriptive instructions
5. Synthesize findings into a review artifact
6. Run a fix loop for safe deterministic fixes
7. Optionally reflect on changes

The review artifact is written to tmp/review/<branch>-review.md.

Phase 0: Validate Companion Skills

Check that required companion skills are installed before dispatching lanes. Inspect these directories for installed skills:

• skills/
• .agents/skills/
• .claude/skills/
• .opencode/skills/
• .cursor/skills/
• .github/skills/

For each detected stack, load its stack reference file (stacks/<stack>.md) and check the companion skill mappings section. For each required skill:

1. Check if it exists in any of the skill directories above
2. If missing, record it with its apm install command

If all skills are installed: Proceed to Phase 1 without warnings.

If skills are missing: Display which skills are missing, provide apm install commands for each, and ask the user whether to:

• Install the missing skills now and retry validation
• Continue with native fallback for affected lanes
• Abort the review

Phase 1: Scope Detection

Determine the review scope from changed files:

BASE_BRANCH=$(git remote show origin | sed -n '/HEAD branch/s/.*: //p')
git diff "${BASE_BRANCH:-main}"...HEAD --name-only
git status --porcelain

Combine both outputs to get the full list of changed files. Detect the base branch from origin/HEAD, falling back to main only when that cannot be resolved.