Speckit.reviewer

Skill wedabro/bro-skills/.agents/skills/speckit.reviewer

bro-skills - Spec-Driven Development CLI

Install

npx -y skills add wedabro/bro-skills --skill speckit.reviewer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Code Reviewer - Review code according to spec and best practices.

SKILL.md

1.2 KB, as published. Nobody here has run it

🎯 Mission

Review implementation code → ensure correct spec, security, performance.

📥 Input

Source code (implemented files)
.agent/specs/[feature]/spec.md + plan.md
.agent/memory/constitution.md

📋 Protocol

Spec Compliance: Does the code correctly implement all requirements in the spec?
Error Handling: Does every API route have try-catch? Is return in the correct error format?
Security: Find injection risks, missing auth checks, exposed secrets.
Performance: Found N+1 queries, awaiting waterfalls, missing pagination.
Constitution: Does the code violate any rules in constitution.md?

Output: Verdict + table findings:

| File:Line | Severity | Issue | Suggestion |
|-----------|----------|-------|------------|
| api/users.ts:45 | 🔴 | Missing auth | Add middleware |

Verdict: ✅ APPROVE or ❌ REQUEST CHANGES (with list to fix).

📤 Output

File: .agent/memory/review-report.md

🚫 Guard Rails

DO NOT fix the code yourself — only review and make suggestions.
Each finding MUST have a specific file:line.

Gives 0 of the 12 instructions most code review skills give

Counted across 610 of the 674 authors here whose files we hold, read 2026-08-06

push back with technical reasoning if wrongin 60 of 610, across 24 files
ask for clarification on unclear itemsin 51 of 610, across 16 files
fix critical issues immediatelyin 45 of 610, across 29 files
implement one item at a timein 45 of 610, across 11 files
group findings by severityin 44 of 610, across 43 files
verify feedback against the codebasein 42 of 610, across 8 files
dispatch a code reviewer subagentin 39 of 610, across 23 files
fix important issues before proceedingin 37 of 610, across 22 files
test each fix individuallyin 35 of 610, across 7 files
reply in github comment threadsin 33 of 610, across 5 files
check for security vulnerabilitiesin 31 of 610, across 27 files
factualize corrections without over-explainingin 30 of 610, across 2 files

Said here and by no other author read

check spec compliance
check error handling in api routes
find n+1 queries and missing pagination
check for constitution violations
output verdict and findings table
write report to memory review report file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.