skills.rest
damoke012
damoke012COMMUNITY
Explore all skills by this author →
GitHub

mp-code-review

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

Updated Apr 16, 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/damoke012/eks_code --skill mp-code-review-damoke012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mp-code-review
Source: https://github.com/damoke012/eks_code/tree/main/.claude-env/skills/mp-code-review
Command: npx skills add https://github.com/damoke012/eks_code --skill mp-code-review-damoke012

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? This Skill separates those axes so one cannot mask the other, and runs both checks in parallel sub-agents to keep their contexts clean. ## Core Features & Use Cases - Two-axis review: Evaluates the diff against documented repo standards (plus a Fowler code-smell baseline) and against the originating issue or spec, reported side by side. - Parallel sub-agents: Spawns independent Standards and Spec sub-agents so findings from one axis never pollute or rerank the other. - Flexible fixed point: Reviews changes since any commit, branch, tag, or merge-base using a three-dot git diff. - 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 against the coding standards and the originating issue.

Frequently Asked Questions about mp-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 and its spec?▼

Provide a fixed point such as a commit SHA, branch, tag, or main, and the Skill diffs HEAD against it with a three-dot git diff. It then runs Standards and Spec sub-agents in parallel and reports both axes side by side.

How do I review changes since a specific commit in git?▼

Name the commit, tag, or expression like HEAD~5 as the fixed point. The Skill verifies the ref with git rev-parse, confirms the diff is non-empty, and reviews everything from that merge-base to HEAD.

What happens if there is no spec or issue for the change?▼

The Skill searches commit messages for issue references, checks user-supplied paths, and looks under docs/, specs/, or .scratch/. If nothing is found it asks you, and if no spec exists the Spec sub-agent is skipped and the report notes that.

Does the review work when a repo has no documented coding standards?▼

Yes. A built-in baseline of Fowler code smells from Refactoring chapter 3 always applies, covering Duplicated Code, Feature Envy, Shotgun Surgery, and others. Documented repo standards override the baseline where they conflict.

Why are standards and spec findings reported separately?▼

A change can pass one axis and fail the other, such as clean code implementing the wrong thing. Keeping the reports separate prevents findings from one axis from masking or reranking the other.

Related Skills

Explore More Software Engineering Skills→
U1traVenoU1traVeno

code-review

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

Community
Intermediate
Fatih0234Fatih0234

code-review

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

Community
Advanced
uzumaki-incuzumaki-inc

health

Run code health checks and compute a weighted 0-10 score.

Official
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate