Reviews a git diff against coding standards and the originating spec using parallel sub-agents.
npx skills add https://github.com/wenyue/SmartKit --skill code-review-wenyue
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/wenyue/SmartKit/tree/main/skills/code-review Command: npx skills add https://github.com/wenyue/SmartKit --skill code-review-wenyue
git diff <fixed-point>...HEAD, with upfront validation that the ref resolves and the diff is non-empty. - Spec source discovery: Locates the originating spec from issue references in commit messages, a user-provided path, or files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main — you get a Standards report citing violated conventions and possible code smells, plus a Spec report listing missing requirements and scope creep, each under 400 words. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.High-intent search queries and answers about installing and using this skill.
Provide the fixed point — a commit SHA, branch name, tag, or expression like HEAD~5 — and the review runs against `git diff <fixed-point>...HEAD` using the merge-base. The ref is validated with `git rev-parse` and the diff is checked to be non-empty before the review starts.
It checks files in the repo that document conventions, 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 anything tooling already enforces is skipped.
The review looks for issue references in commit messages, a user-provided path, or spec files under docs/, specs/, or .scratch/. If none exists and the user confirms there is no spec, the Spec sub-agent is skipped and the final report notes that no spec was available.
A change can pass one axis and fail the other — code can follow every convention but implement the wrong thing, or match the spec while breaking project conventions. Keeping the reports separate prevents one axis from masking failures in the other, so findings are never merged or reranked.
The review is built around a diff between HEAD and a fixed point, so it covers committed work on a branch or since a tag. Uncommitted changes would need to be committed first so they appear in the `git diff <fixed-point>...HEAD` output.
U1traVenoReview a git diff against coding standards and the originating spec using parallel sub-agents.
spiriMirrorFix GitHub PR review feedback by implementing, testing, and pushing changes.
cyhinverseRun automated linters and type checkers on Node.js/TypeScript and Python repositories.
sasamukuAutomate pull request reviews with parallel multi-agent analysis and inline GitHub comments.