Two Axis Code Review
Review a branch or pull request on two separate axes, reported side by side and never merged into one ranking. Standards — does the diff follow this repository's written rules (CLAUDE.md, AGENTS.md, CONTRIBUTING, coding standards) plus a baseline of Fowler's code smells? Spec — does it do what the ticket, spec or plan asked, with nothing missing, nothing extra and nothing done wrongly? Draws on Boehm's verification vs validation ("building the product right" vs "building the right product"), Google's code-review practice and Matt Pocock's two-axis review. Covers pinning the diff to a merge bas
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill two-axis-code-reviewgit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/two-axis-code-review ~/.claude/skills/two-axis-code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Two-Axis Code Review Apply this skill when reviewing a change: a branch, a pull request, uncommitted work. It answers two questions separately, because a change can pass one and fail the other: - **Standards** — is it built right? Does the code follow the rules this repository writes down, and is it free of the classic smells? - **Spec** — is it the right thing? Does it do what the ticket, spec or plan asked: all of it, only it, correctly? Code that follows every convention but implements the wrong behaviour passes Standards and fails Spec. Code that does exactly what was asked in a way the codebase forbids passes Spec and fails Standards. Reporting them as one list lets one axis hide the other, so they stay apart from start to finish. ## Core Philosophy **Verification and validation are different questions** (Boehm): "Are we building the product right?" and "Are we building the right product?" Each needs its own source of truth — the standards for the first, the spec for the second. **Scope is the diff.** Review what the change touches, against a fixed point (usually the merge base with the main branch). Problems that were already there are not findings for this change. **A finding is a claim until checked.** Before reporting anything, confirm it against the code: read the lines, run the build, run the relevant tests. Say what the evidence was. An unverified finding wastes the author's time and the reviewer's credibility.
Details
- Skill name
two-axis-code-review- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/two-axis-code-review/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Two Axis Code Review skill do?
Review a branch or pull request on two separate axes, reported side by side and never merged into one ranking. Standards — does the diff follow this repository's written rules (CLAUDE.md, AGENTS.md, CONTRIBUTING, coding standards) plus a baseline of Fowler's code smells? Spec — does it do what the ticket, spec or plan asked, with nothing missing, nothing extra and nothing done wrongly? Draws on Boehm's verification vs validation ("building the product right" vs "building the right product"), Google's code-review practice and Matt Pocock's two-axis review. Covers pinning the diff to a merge bas
How do I install the Two Axis Code Review skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Two Axis Code Review popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
User Segmentation
8Freddy-CHEN-ux/00_claude_skills
Framework for clustering users into behavioral segments and personas. Use when analyzing user cohorts, identifying patterns, and personalizing product features.
Toyota Way
5vnovakovits/claude-skills
Apply Jeffrey Liker's "The Toyota Way — 14 Management Principles from the World's Greatest Manufacturer" (2004; 2nd ed. 2021), the management system behind the Toyota Production System. Covers the 4P model (philosophy, process, people and partners, problem solving) and the 14 principles, the TPS house (just-in-time and jidoka on heijunka, standardised work and kaizen), the wastes (muda, mura, muri, unused creativity) mapped to software, and Toyota product development (chief engineer, set-based design, front-loading). Includes a review mode that scores a process, ways-of-working or governance d
Validate System
8Freddy-CHEN-ux/00_claude_skills
Validate Nexus-v3 system integrity and fix common issues automatically. Load when user mentions "validate system", "check system", or "fix problems". Runs comprehensive checks on folder structure, metadata files, and framework consistency with auto-repair capabilities.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.