Code Health Agent Skill
Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Delegates to the Centinela (QA) agent.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/davepoon/buildwithclaude --skill code-healthThe instruction itself
7 sections, as written by the authorCode Health
Runs a comprehensive code health scan using the Centinela (QA) agent.
When to Use This Skill
- Periodic codebase hygiene check
- Before a release to ensure no dead code or unresolved debt
- After a large refactoring to verify cleanliness
- When onboarding to understand current code quality
What This Skill Does
- Runs the SIGN IN checklist
- Scans for dead code (unused imports, variables, functions, commented-out blocks, unreachable code)
- Checks for outdated and vulnerable dependencies
- Detects code smells (long functions, deep nesting, duplication)
- Audits TODO/FIXME comments for issue references
- Runs the Scan Complete checklist (TIME OUT)
- Writes findings to
docs/reviews/code-health-{date}.md - Prepares findings handoff to Dev agent
How to Use
Basic Usage
/code-health
Example
User: /code-health
Output: A code health report at docs/reviews/code-health-2026-02-23.md with:
- Dead code findings (verified, not false positives)
- Dependency status and vulnerabilities
- Code smell inventory
- TODO/FIXME audit
- Prioritized findings: Critical > Warning > Suggestion
Tips
- Scans all source directories, not just
src/— includestests/and config files - Previous scan findings are compared to track recurring issues
- Findings are verified to avoid false positives from dynamic imports or plugins
Other skills for the same job
different authors, same section of the catalogue
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
How to use it
Take davepoon/code-health from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.