code-review

Topics in the source

• Process
• 1. Pin the fixed point
• 2. Identify the spec source
• 3. Identify the standards sources
• 4. Spawn both sub-agents in parallel
• 5. Aggregate
• Why two axes

Two-axis review of the diff between HEAD and a fixed point the user supplies: Standards: does the code conform to this repo's documented coding standards? Spec: does the code faithfully implement the originating issue / spec? Both axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings. Start every sub-agent with a fresh context window. The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills. Whatever the user said is the fixed point (a commit SHA, branch name, tag, main, HEAD5, etc.). If they didn't specify one, ask for it. Capture the diff command once: git diff ...HEAD (three-dot, so the comparison is against the merge-base). Also note the list of commits via git log ..HEAD --oneline. Before going further, confirm the fixed point resolves (git rev-parse ) and the diff is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents. Look for the originating spec, in this order: 1. Issue references in the commit messages (#123, Closes #45, GitLab !67, etc.), fetched via the workflow in the tracker doc. 2. A path the user passed as an argument.

This is an excerpt. Refer to the complete source and its current requirements.