skills.rest
stevejbickley
stevejbickleyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Reviews a git diff against coding standards and the originating spec using parallel sub-agents.

4|Updated Aug 22, 2025
Search Tags:#code review#pull request#coding standards#code smells#spec compliance#sub-agents#git diff
One-click install
npx skills add https://github.com/stevejbickley/arcbita-geek-seminars --skill code-review-stevejbickley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/stevejbickley/arcbita-geek-seminars/tree/main/sessions/2026-07-29-ClaudeCodeforAppliedSocialScience/starter/.claude/skills/code-review
Command: npx skills add https://github.com/stevejbickley/arcbita-geek-seminars --skill code-review-stevejbickley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often conflate two separate questions — does the code follow the project's standards, and does it actually implement what was asked for — letting one axis mask failures in the other. This Skill separates those concerns into independent parallel reviews of any diff since a fixed point. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (repo conventions plus a Fowler code-smell baseline) and a Spec review (against the originating issue or PRD) as parallel sub-agents, then reports them side by side. - Flexible fixed points: Reviews changes since any commit SHA, branch, tag, or merge-base, validating the ref and diff before spawning agents. - Automatic spec discovery: Locates the originating spec from issue references in commit messages, user-provided paths, or PRD files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main and receive separate Standards and Spec reports, each citing the violated rule or spec line. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.

Frequently Asked Questions about 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 the fixed point (e.g., main) and the skill runs git diff main...HEAD using the three-dot merge-base comparison. It validates the ref and confirms the diff is non-empty before spawning the two review sub-agents.

How does the code review check against the original spec or issue?▼

The Spec sub-agent receives the diff plus the originating spec, found via issue references in commit messages, a user-provided path, or PRD files under docs/, specs/, or .scratch/. It reports missing requirements, scope creep, and incorrect implementations, quoting the spec line for each finding.

What coding standards does the review check against?▼

It checks documented repo standards such as CODING_STANDARDS.md or CONTRIBUTING.md, plus a fixed baseline of Fowler code smells like Duplicated Code, Feature Envy, and Shotgun Surgery. Documented repo standards always override the baseline, and baseline smells are reported as judgement calls.

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

If no spec is found and the user confirms none exists, the Spec sub-agent is skipped and the final report notes that no spec was available. The Standards review still runs normally.

Why does the review report Standards and Spec results separately?▼

A change can pass one axis and fail the other — standards-compliant code can implement the wrong thing, and correct code can violate conventions. Keeping the reports separate prevents one axis from masking failures in the other.

Related Skills

Explore More Software Engineering Skills→
specvitalspecvital
1

commit

Generate bilingual Conventional Commits messages from staged changes and branch context.

Official
Intermediate
jswestjswest
11

ship

Automate pull request creation, merging, and branch promotion in GitHub repositories.

Community
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
euxxeuxx
4

gh-address-comments

Fetch and summarize GitHub pull request review comments for a branch.

Community
Advanced