Skip to content

borghei/Claude-Skills / engineering/code-reviewer

code-reviewer

Verified

Heuristic code-review pre-pass for TS, JS, Python, Go, Swift and Kotlin: PR risk, smells, SOLID issues, and a two-axis (standards vs spec) review method. Use when reviewing a PR or preparing a review checklist.

FileKindSize
SKILL.mdskill md12.0 KB
assets/two-axis-review-template.mdmarkdown1.0 KB
references/code_review_checklist.mdmarkdown6.9 KB
references/coding_standards.mdmarkdown12.1 KB
references/common_antipatterns.mdmarkdown16.1 KB
references/tool_reference.mdmarkdown10.9 KB
references/two-axis-review.mdmarkdown6.3 KB
scripts/code_quality_checker.pyexecutablescript17.1 KB
scripts/pr_analyzer.pyexecutablescript14.2 KB
scripts/review_report_generator.pyexecutablescript17.5 KB
scripts/review_scope.pyexecutablescript7.9 KB

assets/two-axis-review-template.md

View on GitHub
# Review: <branch or PR title>

**Base:** `<base ref>` (`<base sha>`)  ·  **Head:** `<head sha>`  ·  **Diff:** `git diff <base>...<head>`
**Commits:** <n>  ·  **Files:** <n>  ·  **Lines changed:** <n>
**Spec source:** <path, issue link, or "none found">
**Standards sources:** <files>

## Standards

<Report from the standards pass, lightly cleaned. One finding per bullet.>

- `<file:line>` — <what is wrong>. Rule: <source file> — "<rule>". **Hard** | **Judgement**

**Summary:** <n> findings; most serious: <one line>.

## Spec

<Report from the spec pass. Quote the spec line for every finding.>

### Missing or partial
- "<spec line>" — <what is missing>

### Not asked for
- `<file:line>` — <behaviour>. Bucket: enabling | unrequested | speculative

### Built wrongly
- "<spec line>" — <how the implementation differs>

**Summary:** <n> findings; most serious: <one line>.

## Overlaps

- <finding raised by both passes, listed once here>

## Verdict

**<Approve | Request changes | Block>** — <one sentence naming the deciding finding(s)>
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall