dev-code-review

Reviews git diffs against coding standards and original specs using parallel subagents.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill dev-code-review-choi-keith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-code-review
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/dev-skills/dev-backend/skills/dev-code-review
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill dev-code-review-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often check only one dimension—either style or correctness—letting defects slip through when code follows conventions but misses requirements, or implements the spec while violating project standards. This Skill runs both checks in parallel so neither axis masks the other. ## Core Features & Use Cases - Dual-Axis Review: Evaluates a diff against documented repository coding standards (Standards axis) and against the original issue or spec (Spec axis) in separate parallel subagents. - Fowler Smell Baseline: Applies a built-in catalog of twelve code smells from Refactoring (Duplicated Code, Feature Envy, Shotgun Surgery, etc.) even when the repository has no documented standards. - Automatic Spec Discovery: Locates the original spec from issue references in commit messages, user-provided paths, or files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main; you receive two side-by-side reports—one citing violated standards with file and hunk references, one listing missing or out-of-scope spec requirements. ## Quick Start Ask the agent to review the changes since main using the dev-code-review skill and report standards and spec findings separately.

Frequently Asked Questions about dev-code-review

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

FAQPage Schema
How do I review all changes on a branch since main?

Provide a fixed point such as main, a commit SHA, tag, or HEAD~5, and the skill diffs it against HEAD using the three-dot merge-base form. It validates the ref and confirms the diff is non-empty before starting the review.

How does automated code review check both style and requirements?

It runs two parallel subagents: a Standards agent checks the diff against documented repository conventions plus a Fowler code-smell baseline, while a Spec agent verifies the diff faithfully implements the original issue. Results are reported separately so neither axis hides the other.

What happens if there is no spec for the changes being reviewed?

The skill searches commit messages for issue references, user-provided paths, and files under docs/, specs/, or .scratch/. If no spec exists, the Spec subagent is skipped and the final report notes that no spec was available.

Does this code review work without documented coding standards?

Yes. A built-in baseline of twelve Fowler code smells from Refactoring applies even with no repository documentation. Documented repository standards always take priority and can suppress baseline findings they endorse.

Why are standards and spec findings reported separately instead of merged?

A change can pass one axis and fail the other—clean code implementing the wrong thing, or correct behavior violating conventions. Keeping the reports separate prevents one axis from masking failures in the other and avoids cross-axis re-ranking.