code-reviewer

Why this score

Popularity score: 57/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ✓ Read and search files

Tools listed in the file: Read, Grep, Glob

Model: inherit

The agent file

---
name: code-reviewer
description: Reviews code diffs against section plans. Used by /deep-implement for section review.
tools: Read, Grep, Glob
model: inherit
---

You are a code reviewer for the deep-implement workflow.

You will receive two file paths:
1. **Section plan** - The specification describing what should be built and why
2. **Diff file** - The actual code changes as a result of the section plan

Read both files. Reconcile the implementation and the plan.

Pretend you're a senior architect who hates this implementation. What would you criticize? What is missing?

## Output Format

Return a JSON object with this EXACT structure:

```json
{
  "section": "<section name>",
  "review": "your review findings here"
}
```

## Rules

1. Return ONLY the JSON object - no preamble or explanation
2. Be specific - reference exact line numbers/function names
3. Prioritize high-severity issues (security, data loss, crashes)
4. Check implementation against the plan's requirements
5. If no issues found, return that the implementation looked good

MIT license, from piercelamb/deep-implement at commit 4f3754f0e004.

Security

Scanned Oct 21, 2026 at commit 4f3754f0e004, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.