skills.rest
Manuel-Gartenkrot-Casal
Manuel-Gartenkrot-CasalCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Reviews git diffs against coding standards and originating specs using parallel sub-agents.

2|Updated May 9, 2026
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/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence --skill code-review-manuel-gartenkrot-casal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence --skill code-review-manuel-gartenkrot-casal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a branch or PR requires checking two separate things — whether the code follows the repo's documented standards and whether it actually implements what the issue or PRD asked for — and doing both in one pass causes one concern to mask the other. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo conventions plus a Fowler code-smell baseline) and a Spec review (fidelity to the originating issue or PRD) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Reviews changes since any commit, branch, tag, or merge-base using three-dot git diff, with upfront validation that the ref resolves and the diff is non-empty. - Spec discovery: Automatically 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, with a per-axis summary of the worst finding. ## Quick Start Ask the assistant to review the changes on the current 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 a branch against coding standards before merging?▼

Provide a fixed point such as main, a tag, or a commit SHA, and the skill diffs HEAD against it using a three-dot merge-base comparison. A Standards sub-agent checks the diff against documented repo conventions plus a baseline of Fowler code smells.

How do I check if code matches the original issue or PRD?▼

The Spec axis locates the originating spec from issue references in commit messages, a user-provided path, or PRD files under docs/, specs/, or .scratch/. A sub-agent then reports missing requirements, scope creep, and incorrect implementations, quoting the spec line for each finding.

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

If no spec is found after checking commit references, user arguments, and docs directories, the skill asks the user where it is. If there is none, the Spec sub-agent is skipped and the final report notes that no spec was available.

Why does the review run standards and spec checks separately?▼

A change can follow every coding standard but implement the wrong thing, or match the spec while breaking project conventions. Running the axes as parallel sub-agents and reporting them separately prevents one axis from masking failures in the other.

What code smells does the standards review detect?▼

The baseline covers twelve Fowler smells including Duplicated Code, Feature Envy, Data Clumps, Primitive Obsession, Shotgun Surgery, and Speculative Generality. Each is reported as a labelled judgement call, and documented repo standards always override the baseline.

Related Skills

Explore More Software Engineering Skills→
Maple-and-SpruceMaple-and-Spruce

git-workflow

Standardize Git workflows with branch naming, conventional commits, and PR processes.

Official
Intermediate
Fatih0234Fatih0234

code-review

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

Community
Advanced
zajcazajca
2

go-linting

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

Community
Basic
summarybotngsummarybotng
2

code-review-quality

Conduct context-driven code reviews focusing on quality, testability, and maintainability.

Official
Advanced