code-review

Review Git diffs against coding standards and specifications.

11|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/romiluz13/auto-pi --skill code-review-romiluz13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/romiluz13/auto-pi/tree/main/skills/code-review
Command: npx skills add https://github.com/romiluz13/auto-pi --skill code-review-romiluz13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill separates code review into standards and specification checks, helping identify implementation defects, scope gaps, coding-standard violations, and maintainability risks without allowing one review axis to mask the other.

Core Features & Use Cases

  • Fixed-Point Diff Review: Reviews changes from a specified commit, branch, tag, merge-base, or other Git reference.
  • Two-Axis Analysis: Runs standards and spec reviews independently, including documented repository conventions, code smells, friction signals, and AI-generated anti-pattern checks.
  • Workflow Guardrails: Validates the Git reference and diff before review, identifies the originating specification, uses parallel sub-agents, and reports findings with separate summaries.
  • Use Case: Ask it to review a feature branch against main and compare the implementation with its issue or product specification.

Quick Start

Use the code-review skill to review all changes on my current branch since main against the originating issue and repository coding standards.

Frequently Asked Questions about code-review

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

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

Review a pull request by analyzing the Git diff against documented coding standards and the originating specification to identify defects, omissions, scope creep, and maintainability risks.

Can I check my feature branch for code smells and AI-generated anti-patterns?

Yes, checking a feature branch for code smells and AI-generated anti-patterns is done by evaluating a fixed-point Git diff to detect friction signals and maintainability risks.

How does reviewing code changes against a specification prevent scope creep?

Reviewing code changes against a specification prevents scope creep by running a two-axis analysis that independently checks the implementation for standards violations and spec gaps.

What is the best way to automate defect identification in a Git diff?

Automate defect identification in a Git diff by validating a resolvable Git reference and running parallel sub-agents to report standards and specification findings with separate summaries.

Do I need an issue or specification source to review a work-in-progress branch?

An issue or specification source is required to review a work-in-progress branch when applicable, ensuring the implementation is checked for omissions and specification compliance.

What happens if my Git reference is invalid or the diff is empty before a code review?

If a Git reference is invalid or the diff is empty, workflow guardrails halt the code review because a resolvable Git reference and a non-empty three-dot diff are required prerequisites.