code-reviewer

Review codebases for health, quality, test coverage, and specification compliance.

Updated Feb 11, 2026

Search Tags:#code quality #code review #technical debt #test coverage #code audit #SOLID principles

Ready to run

npx skills add https://github.com/juniorfontenele/ai-guidelines --skill code-reviewer-juniorfontenele

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/juniorfontenele/ai-guidelines/tree/main/.agents/skills/code-reviewer
Command: npx skills add https://github.com/juniorfontenele/ai-guidelines --skill code-reviewer-juniorfontenele

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive analysis of your codebase, identifying potential issues related to code health, quality, test coverage, and specification compliance, helping to maintain high engineering standards.

Core Features & Use Cases

Code Health Audit: Detects dead code, code smells, and SOLID violations.
Quality & Compliance Check: Assesses adherence to coding standards and project specifications.
Test Quality Analysis: Evaluates test completeness, path coverage, and adherence to best practices.
Use Case: Before merging a significant feature, use this Skill to perform a deep review, ensuring the code is robust, maintainable, and meets all project requirements, generating a detailed report of findings.

Quick Start

Perform a full review of the current codebase.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I perform a deep code review to check for SOLID violations and dead code?▼

Deep code review to check for SOLID violations and dead code is performed by auditing the codebase to assess code health, engineering quality, and specification compliance. It identifies issues like dead code, overengineering, and SOLID violations, generating a structured report with severity ratings.

What is the best way to audit technical debt and test coverage gaps before a merge?▼

Auditing technical debt and test coverage gaps before a merge is best handled through a comprehensive codebase review. It evaluates test completeness, path coverage, and adherence to best practices, identifying specification deviations and outputting a detailed report with actionable next steps.

Can I assess project specification compliance and code smells automatically across my codebase?▼

Assessing project specification compliance and code smells automatically across your codebase is supported by a full code health audit. It detects deviations from project specifications, identifies code smells, and generates a structured report with severity ratings and actionable next steps.

Does a code quality audit detect overengineering and test coverage gaps in large codebases?▼

A code quality audit does detect overengineering and test coverage gaps in large codebases. It conducts a deep review to evaluate engineering quality, test completeness, and path coverage, ensuring the code is robust and maintainable while generating a detailed report of findings.

When do I need a code health audit to evaluate engineering quality?▼

You need a code health audit to evaluate engineering quality before merging a significant feature. It performs a deep codebase review to identify code smells, SOLID violations, and test coverage gaps, ensuring the code is robust, maintainable, and meets all project requirements.