codebase-review

Reviews an entire codebase across multiple axes and reports evidence-backed findings with severity ratings.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/psw7205/skills --skill codebase-review-psw7205
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-review
Source: https://github.com/psw7205/skills/tree/main/skills/codebase-review
Command: npx skills add https://github.com/psw7205/skills --skill codebase-review-psw7205

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Whole-codebase reviews often produce vague, speculative findings or drown in false positives, making it hard to know what is actually worth fixing. This Skill performs a read-only, multi-axis review (architecture, refactoring, readability, performance, robustness, security, tests, consistency) where every finding is anchored to a concrete file:line and severity level. ## Core Features & Use Cases - Survey-first mapping: Identifies stack, entry points, and hotspots (git churn, file size, dependency concentration) before deep review, and runs non-destructive tools (type checkers, linters, audit, dead-code detectors) to ground findings. - False-positive suppression: Applies a Pre-Report Gate, Quote-the-line rule for High/Critical findings, and a blacklist of common LLM review hallucinations so only defensible issues are reported. - Structured output: Groups deduplicated findings by severity with confidence, effort, and autofix labels, plus triage groups, coverage disclosure, and an improvement roadmap. - Use Case: Ask for a full review of a legacy service before a refactor; receive a prioritized list of real defects (e.g., a swallowed fetch error at a specific line) that can be handed off to a fix loop. ## Quick Start Review this entire codebase across architecture, performance, security, and tests, and give me a severity-ranked list of findings with file and line evidence.

Frequently Asked Questions about codebase-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an entire codebase for quality issues?▼

Request a full codebase review and the Skill first maps the project structure and hotspots, then checks eight axes including architecture, performance, security, and tests. Every finding is reported with a file:line citation, severity, and confidence level.

What is the difference between a codebase review and a diff review?▼

A codebase review examines the whole project across multiple quality axes, while a diff review only examines a specific change set such as staged changes or a pull request. Use codebase review for broad audits and diff review for recent changes.

How does automated code review avoid false positives?▼

Each finding must pass a Pre-Report Gate requiring a citable file:line, a named failure mode, read surrounding context, and a defensible severity. High and Critical findings must quote the exact offending line verbatim or be downgraded.

Does the codebase review modify my code?▼

No, the review is strictly read-only and never edits files during the review phase. If you want fixes applied afterward, the findings are handed off to a separate review-fix-verify-commit loop with an explicit scope.

Can codebase review handle large repositories?▼

Yes, it scales depth by repository size: small repos get a single full pass, medium repos focus on hotspots, and large repos use parallel per-axis subagents with shallow coverage of remaining areas disclosed in the report.

When should I not use a full codebase review?▼

Skip it when you only need a specific diff or PR examined, or when your intent is to fix code immediately rather than audit. Those cases are better served by a diff review or a direct fix workflow.