Loading...
Loading...
Found 20 Skills
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests.
Before declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently modified code.
Identify unused code, imports, variables, and functions for safe removal.
Remove code comments via natural language guidance, suitable for simple scenarios in languages such as Python, JavaScript, TypeScript (.ts/.tsx), Java, C/C++, Go, HTML, etc.
Remove AI code slop
Use this when the user asks to refactor, clean up, optimize, or improve code quality.