afk-code-review

Two-axis review of the requested branch, PR, commit, or working-tree changes:

• Standards - does the code conform to this repo's documented coding standards?
• Spec - does the code faithfully implement the originating issue, spec, or implementation ticket?

Both axes should run in parallel sub-agents or fresh contexts so they do not pollute each other's context, then this skill aggregates their findings.

Process

1. Pin the review scope

Resolve the requested scope before collecting evidence:

• Branch or PR: use the supplied base or PR base and git diff <base>...HEAD; record commits with git log <base>..HEAD --oneline.
• Commit: inspect the specified commit's change; resolve the intended parent comparison for a merge commit.
• Working tree: include staged changes (git diff --cached), unstaged changes (git diff), and relevant untracked files (git ls-files --others --exclude-standard). Inspect untracked file contents directly; Git diffs omit them.

Reuse the scope supplied by the user or PR metadata. Ask only when multiple interpretations remain materially different. Verify refs resolve, record the exact comparison commands and file inventory, and report an empty scope without launching reviewers. An empty tracked diff alone does not establish an empty working-tree scope.