Reviews a codebase for style consistency, patterns, idioms, and adherence to KISS, DRY, POLA, YAGNI principles. Automatically detects languages/frameworks present and applies appropriate analysis. Produces analysis findings and uses pm7y-ralph-planner to generate TASKS.md for autonomous execution.
View on GitHubpm7y/pm7y-marketplace
pm7y-claude-code
skills/pm7y-codebase-review/SKILL.md
January 22, 2026
Select agents to install to:
npx add-skill https://github.com/pm7y/pm7y-marketplace/blob/main/skills/pm7y-codebase-review/SKILL.md -a claude-code --skill pm7y-codebase-reviewInstallation paths:
.claude/skills/pm7y-codebase-review/# Codebase Review Skill Reviews codebases for consistency, patterns, and adherence to software engineering principles. Produces analysis findings that are passed to `pm7y-ralph-planner` for TASKS.md generation. --- ## Overview This skill performs comprehensive codebase analysis focusing on: - **Style & pattern consistency** - Implicit and explicit conventions - **Language idioms** - Following best practices for each language - **Principle adherence** - KISS, DRY, POLA, YAGNI - **Complexity reduction** - Identifying unnecessary complexity - **Duplication detection** - Finding repeated code patterns **Output:** Analysis findings passed to `pm7y-ralph-planner`, which generates a `TASKS.md` file with validation requirements and learnings tracking for autonomous execution via `pm7y-ralph-loop`. **When to use:** - Periodic codebase health checks with automated fixes - Before major refactoring efforts - Autonomous code quality improvement sessions - After rapid feature development to address technical debt --- ## Review Depth Options The review supports different depth levels via command arguments: | Depth | Scope | Use When | |-------|-------|----------| | `--quick` | Sample key files, high-level patterns | Quick health check | | `--standard` | Representative files from each area | Regular reviews (default) | | `--comprehensive` | Full codebase scan, detailed analysis | Before major refactoring | --- ## Review Process ### Step 1: Study Documentation Before analyzing code, read and understand: 1. **README.md** - Project overview, architecture decisions 2. **CLAUDE.md** - Codebase conventions (if exists) 3. **CONTRIBUTING.md** - Contribution guidelines 4. **Architecture docs** - Any docs in `/docs` or similar 5. **.editorconfig** - Formatting preferences 6. **Linter configs** - ESLint, Prettier, StyleCop, .pylintrc, .rubocop.yml, etc. Use these to understand the project's stated conventions before comparing to actual code. ### Step 2: Detect Languages and