code-health

1# Code Health
2 
3Runs a comprehensive code health scan using the Centinela (QA) agent.
4 
5## When to Use This Skill
6 
7- Periodic codebase hygiene check
8- Before a release to ensure no dead code or unresolved debt
9- After a large refactoring to verify cleanliness
10- When onboarding to understand current code quality
11 
12## What This Skill Does
13 
141. Runs the SIGN IN checklist
152. Scans for dead code (unused imports, variables, functions, commented-out blocks, unreachable code)
163. Checks for outdated and vulnerable dependencies
174. Detects code smells (long functions, deep nesting, duplication)
185. Audits TODO/FIXME comments for issue references
196. Runs the Scan Complete checklist (TIME OUT)
207. Writes findings to `docs/reviews/code-health-{date}.md`
218. Prepares findings handoff to Dev agent
22 
23## How to Use
24 
25### Basic Usage
26 
27```
28/code-health
29```
30 
31## Example
32 
33**User**: `/code-health`
34 
35**Output**: A code health report at `docs/reviews/code-health-2026-02-23.md` with:
36- Dead code findings (verified, not false positives)
37- Dependency status and vulnerabilities
38- Code smell inventory
39- TODO/FIXME audit
40- Prioritized findings: Critical > Warning > Suggestion
41 
42## Tips
43 
44- Scans all source directories, not just `src/` — includes `tests/` and config files
45- Previous scan findings are compared to track recurring issues
46- Findings are verified to avoid false positives from dynamic imports or plugins