mcpField
C
code-review

code-review

github.com/darknesskillerTesting & quality0101 installsUpdated 2w ago
Repository

About code-review

A code-review skill for engineers who need repeatable reviews against repository standards and a stated specification. It separates the two review axes and requires findings with file-and-line evidence, fixes, counts, and the worst issue.

Key features

  1. 01Pin and verify the comparison point
  2. 02Locate specifications and repository standards
  3. 03Review standards and spec independently
  4. 04Report evidence, fixes, counts, and worst issues

Use cases

  1. 01Review a branch against its implementation spec
  2. 02Check changes against AGENTS.md or CLAUDE.md
  3. 03Report blocked review access in a defined format

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/darknesskiller/skills --skill code-review

After installing, type/code-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Code Review

Steps

  1. Pin fixed point. Use supplied ref. Otherwise upstream then merge-base with default. Confirm git rev-parse works, git diff non-empty.

  2. Find spec. Check issue refs in commits/branch names, then paths, docs/, specs/, PR descriptions. No spec: "no spec available".

  3. Find standards. Read AGENTS.md, CLAUDE.md, CONTEXT.md, relevant skills. Apply repo standards first.

  4. Run review. Review Standards, then Spec. One axis must not rerank the other.

  5. Report. ## Standards and ## Spec headings. file:line evidence and fixes. Counts per axis. Worst issue per axis.

Output

If access is blocked, say so under these headings: Comparison point, Files, Counts, and Worst issue.

Completion: report has both headings, file:line evidence, fixes, counts, worst issue.

Comments

Markdown supported