review

Review code diffs against repository standards and originating specifications.

12|4|Updated May 14, 2012
One-click install
npx skills add https://github.com/sethvoltz/dotfiles --skill review-sethvoltz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sethvoltz/dotfiles/tree/main/claude/claude/skills/review
Command: npx skills add https://github.com/sethvoltz/dotfiles --skill review-sethvoltz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reviews code changes without conflating code quality with intent, so you can tell whether a branch is standards-compliant, spec-correct, or both.

Core Features & Use Cases

  • Dual-axis review: Separates repository standards from the originating specification so each concern is judged independently.
  • Flexible diff handling: Supports local branch reviews, fixed-point comparisons, and open pull requests.
  • Structured reporting: Produces side-by-side findings for Standards and Spec, helping teams review work-in-progress, PRs, and feature branches with clarity.

Quick Start

Use the review skill to inspect the current branch and report Standards and Spec findings side by side.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request against both coding standards and original specifications?

Review a pull request by comparing the code diff against documented repository standards and the originating intent independently. This dual-axis approach reports standards compliance and specification correctness side by side without conflating the two concerns.

What is the best way to separate code quality checks from intent validation during a branch review?

Separate code quality from intent validation by running isolated parallel analyses on the branch diff. This dual-axis method judges repository standards and specification findings independently, ensuring code quality is not conflated with feature intent.

Can I use this code review approach for local branches and fixed-point revisions, or only open pull requests?

You can use this code review approach for local branch reviews, fixed-point revisions, and open pull requests. Flexible diff handling supports multiple stages of work-in-progress validation and feature branch inspection.

How does dual-axis diff analysis work when reviewing work-in-progress code changes?

Dual-axis diff analysis works by collecting the diff, discovering the spec source, and running isolated parallel analysis. It reports standards and specification findings independently, providing structured side-by-side results for work-in-progress validation.

Do I need separate diff collection and spec source discovery to review code changes?

You need separate diff collection and spec source discovery to review code changes effectively. Isolated parallel analysis of these inputs allows the system to report standards compliance and specification correctness independently without conflating results.

When should I not use a dual-axis code review for my feature branch?

You should not use dual-axis code review if your repository lacks documented standards or a clear originating specification. The method requires both a diff and a spec source to produce independent standards and specification findings.