two-axis-review

Name: two-axis-review
Availability: InStock
Author: Andrew

Review repository diffs against standards and spec sources.

2|Updated Jun 19, 2026

Search Tags:#git #diff analysis #code review #pull request #standards #spec review

Ready to run

npx skills add https://github.com/andrewthetechie/andrew-skills --skill two-axis-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: two-axis-review
Source: https://github.com/andrewthetechie/andrew-skills/tree/main/two-axis-review
Command: npx skills add https://github.com/andrewthetechie/andrew-skills --skill two-axis-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review code changes against both the project’s documented standards and the originating spec, so you can catch implementation mistakes, missing requirements, and scope drift before merging.

Core Features & Use Cases

Standards Review: Checks diffs against repo conventions, ADRs, and coding guidance to flag violations that tooling may not catch.
Spec Review: Compares the change set to the issue, PRD, or spec to identify missing requirements, partial implementations, and unrequested behavior.
Use Case: A developer asks for a review of a branch since main, and this Skill produces separate findings for standards compliance and spec fidelity.

Quick Start

Ask me to review your branch or diff against a specific base like main or a commit, and I will assess it separately for standards and spec alignment.

Frequently Asked Questions about two-axis-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review a git diff against project standards and a pull request spec?▼

To review a git diff against project standards and a pull request spec, you compare the code changes to repository conventions and the originating spec. This produces separate findings for standards compliance and requirement fidelity.

Can I check a branch for missing requirements and scope drift before merging?▼

Checking a branch for missing requirements and scope drift involves comparing the diff to the originating spec or PRD. This spec review identifies partial implementations and unrequested behavior before the code is merged.

How does standards review work for code changes in a repository diff?▼

Standards review for code changes checks the repository diff against documented conventions, ADRs, and coding guidance. It flags standards violations that automated tooling may not catch during regular linting.

What is the best way to review work-in-progress commits compared with main?▼

Reviewing work-in-progress commits compared with main requires evaluating the diff against a fixed point. This two-axis process assesses both standards compliance and spec fidelity separately.

What do I need to locate before reviewing a repository diff for spec mismatches?▼

Before reviewing a repository diff for spec mismatches, you need to locate the repository standards sources and the spec source. These provide the baseline to produce separate code quality and requirement findings.

Does this code review process work with branches and tags or only pull requests?▼

This code review process works with branches, pull requests, work-in-progress changes, and commits. It compares these against main, a tag, or another revision to identify standards violations and spec mismatches.