codebase-review

Audit entire codebases for duplicated logic and quality issues.

89|7|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/nikhilsitaram/claude-caliper --skill codebase-review-nikhilsitaram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-review
Source: https://github.com/nikhilsitaram/claude-caliper/tree/main/skills/codebase-review
Command: npx skills add https://github.com/nikhilsitaram/claude-caliper --skill codebase-review-nikhilsitaram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you find repository-wide code quality problems that single-branch reviews miss, such as duplicated logic, dead code, over-abstraction, naming drift, and inconsistent patterns across modules.

Core Features & Use Cases

  • Whole-repo auditing: Reviews an entire codebase or a scoped directory to surface cross-module issues.
  • Quality-focused findings: Flags DRY violations, YAGNI problems, complexity hotspots, refactoring opportunities, and consistency gaps with severity levels.
  • Review routing: Separates inline fixes from complex follow-up work so teams can decide whether to implement directly, open issues, or draft plans.
  • Use case: Run it before a major refactor or after a long development phase to uncover accumulated technical debt and cross-directory drift.

Quick Start

Use the codebase-review skill to audit the repository for DRY, YAGNI, complexity, naming drift, and cross-directory inconsistencies.

Frequently Asked Questions about codebase-review

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

FAQPage Schema
How do I find duplicated logic and technical debt across my whole codebase?

Find duplicated logic and technical debt across your whole codebase by running a repository-wide audit that detects cross-directory drift, DRY violations, and dead code missed by single-branch reviews. The audit outputs severity-classified findings with explicit file citations.

What is a repository audit and how does it detect cross-directory drift?

A repository audit is a comprehensive code quality review that detects cross-directory drift, naming inconsistencies, and over-abstraction. It works by analyzing entire codebases or scoped directories to surface accumulated technical debt that standard per-task reviews miss.

How do I identify YAGNI violations and refactoring opportunities before a major refactor?

Identify YAGNI violations and refactoring opportunities before a major refactor by performing a pre-refactor assessment of the entire repository. This surfaces complexity hotspots and over-abstraction, separating inline fixes from complex follow-up work.

Can I scope a code review to a specific directory instead of the whole repository?

Yes, you can scope a code review to a specific directory instead of the whole repository. The audit supports both whole-repo and scoped directory reviews to surface cross-module issues, DRY violations, and consistency gaps with severity levels.

How are code review findings routed for inline fixes versus deferred follow-up work?

Code review findings are routed by separating inline fixes from complex follow-up work, providing routeable findings with explicit file citations and severity classification. This allows teams to decide whether to implement directly, open issues, or draft plans.