mcpbeat

Code Health

davepoon/code-health

Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Delegates to the Centinela (QA) agent.

398 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3248
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/davepoon/buildwithclaude --skill code-health

The instruction itself

7 sections, as written by the author

Code 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/ — includes tests/ and config files
  • Previous scan findings are compared to track recurring issues
  • Findings are verified to avoid false positives from dynamic imports or plugins

How to use it

Copy the folder

Take davepoon/code-health from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.