p:code-review

Analyze code files recursively and report quality issues with severity levels.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/pontscho/prompt-heaven --skill p-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: p:code-review
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Acode-review
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases often accumulate technical debt and inconsistent quality across files and modules, making maintenance costly and risky.

Core Features & Use Cases

  • Automated evaluation of readability, structure, error handling, naming, and conformance to project rules.
  • Actionable findings with severity levels to guide refactoring decisions.
  • Targeted reviews of single files or entire directories with depth control and non-code filtering.

Quick Start

Review the target path and return a structured report detailing readability, structure, and maintainability findings.

Frequently Asked Questions about p:code-review

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

FAQPage Schema
How do I analyze code quality across an entire project directory?

You can analyze code quality across a directory by recursively scanning files up to a configurable depth, filtering out non-code artifacts, and gathering metrics on readability, structure, error handling, naming, and maintainability.

Can I get severity levels for code review findings to guide refactoring?

Yes, code review findings are output as structured results with severity levels, helping you prioritize and guide refactoring decisions for technical debt and inconsistent quality issues.

Does static analysis work across different programming languages?

Static analysis works across languages by analyzing files recursively and filtering non-code artifacts, gathering metrics on readability, structure, error handling, naming, and maintainability regardless of language.

What is the best way to assess readability and maintainability issues in my codebase?

The best way to assess readability and maintainability is to run an automated evaluation on your target path, which returns a structured report detailing findings with actionable severity levels.

Can I review a single file instead of a full directory for code quality issues?

Yes, you can perform targeted reviews of single files or entire directories with depth control and non-code filtering to identify and quantify code quality issues.

What metrics does a code quality review evaluate?

A code quality review evaluates readability, structure, error handling, naming conventions, and maintainability, producing structured results with severity levels to identify technical debt and guide refactoring.