crap
Rank functions by CRAP score (complexity × lack of real test coverage) on the current branch, then propose either a refactor or missing tests for the worst offender. Use when the user runs /crap or asks to find risky, complex, poorly-tested code.
72
Quality
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Securityby
Passed
No known issues
No security issues found
Scanned
- Repository
- belchman/claude-skills
- Commit
be88d6c
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.