review

Review Skill

You are entering the review phase. You will perform a comprehensive code review using 8 parallel review agents, each examining the code from a different perspective.

Configuration

Learnings Directory Lookup:

1. First, check for project-local learnings at <git-root>/.llm/learnings/
2. If not found, fall back to [paths.learnings_directory] from ~/.agentic-eng/config.toml

This allows each project to have its own learnings while maintaining backwards compatibility.

Process

Step 1: Detect Stack Structure

Detect the active stack workflow using the git-stacks KB partition as the shared source of truth:

1. list_kb_documents for partition git-stacks

2. read_kb_document_by_path for /index.md

3. Run the dedicated-client checks from git-stacks/index.md

   • If a dedicated client is detected, record STACK_CLIENT accordingly
   • If no dedicated client is detected, inspect the current branch, the plan's PR Stack section, and GitHub base refs to determine whether this repo is using a native git stack
   • If you confirm a native stack, record STACK_CLIENT=native-git
   • If you cannot confirm a stack, fall back to standard single-PR review

4. Load the matching KB client doc before running any stack-specific command:

   • charcoal → read_kb_document_by_path for /charcoal.md
   • git-town → read_kb_document_by_path for /git-town.md
   • native-git → read_kb_document_by_path for /native-git.md
   • Use the client doc as the source of truth for stack-specific commands. Never assume gt exists unless you detected it.

If a stack is detected:

• Parse the stack to get list of branches and their parent relationships
• Each branch in the stack is a separate PR to review

Step 1.5: Choose Review Scope (Stacked PRs Only)

If in a stack with multiple branches, ask the user:

## Stack Detected

Your stack has N PRs:
| PR | Branch | Description |
|----|--------|-------------|
| 1  | feat/part-1 | [from commits] |
| 2  | feat/part-2 | [from commits] |
| 3  | feat/part-3 | [from commits] |

How would you like to review?
1. Review all PRs (recommended) - Reviews each PR against its parent
2. Review current PR only - Reviews only the current branch
3. Review entire stack as one diff - Reviews all changes from main to HEAD