skills.rest
nejcm
nejcmCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Reviews code diffs against specs and repo standards with severity-ranked findings.

1|Updated Jul 3, 2026
Search Tags:#code review#pull request#code smells#spec compliance#merge readiness#git diff#severity
One-click install
npx skills add https://github.com/nejcm/agents --skill code-review-nejcm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nejcm/agents/tree/main/skills/code-review
Command: npx skills add https://github.com/nejcm/agents --skill code-review-nejcm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a structured, read-only review of branches, PRs, or commit ranges so defects, missing requirements, and standards violations are caught before merge without the reviewer editing code. ## Core Features & Use Cases - Two-axis review: Evaluates changes against the spec (missing requirements, scope creep, incorrect implementations) and against repo standards plus a fixed Fowler code-smell baseline. - Severity-ranked reporting: Classifies findings as Critical, Important, or Minor with file:line references, rationale, and fix guidance, ending in a merge-readiness verdict. - Subagent delegation: Dispatches independent spec and standards reviewers with crafted briefs, then aggregates results without merging the axes. - Use Case: Before merging a feature branch, run the review against origin/main to receive a report of unmet requirements, code smells like duplicated logic or feature envy, and a clear ready-to-merge assessment. ## Quick Start Review the changes on my current branch against origin/main and tell me whether it is ready to merge.

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 or PR before merging?▼

Provide a fixed baseline such as origin/main or a commit SHA, and the review diffs that range against HEAD. Findings are reported by severity with file:line references and a ready-to-merge verdict, without modifying any code.

What does a code review check besides the requirements?▼

Beyond spec compliance, it checks documented repo standards from files like AGENTS.md or CONTRIBUTING.md, plus a fixed baseline of Fowler code smells such as duplicated code, feature envy, and shotgun surgery.

Can code review run without a written spec or requirements document?▼

Yes. If no spec is found in user input, commits, or docs directories, the spec axis is reported as no spec available and the review infers intent from commit messages and the diff itself.

Does the review fix the issues it finds?▼

No, it is read-only and reports findings rather than fixing them. Fixes happen only when the user explicitly requests review-and-fix or approves the findings, with Critical issues addressed first.

When should I run a code review during development?▼

Run it after meaningful task batches or risky changes, after completing a major feature, and always before merging to main. It is also useful before refactoring to establish a baseline or after fixing a complex bug.

Related Skills

Explore More Software Engineering Skills→
jwh3timesjwh3times
1

implement

Implements work from specs or tickets using TDD, code review, and PR shipping.

Community
Intermediate
sdcorejssdcorejs
2

sdcorejs-repair-loop

Verify, fix, and re-verify review findings until Critical and Important items resolve.

Community
Advanced
Euda1mon1aEuda1mon1a

automated-code-fixer

Detect and correct code defects across test suites, linters, type checkers, and security scanners.

Community
Advanced
ZaxbyHubZaxbyHub

review-finding-validator

Validates code review findings against current worktree evidence before implementation.

Official
Intermediate