Loading...
Loading...
Found 63 Skills
Identify unused code, imports, variables, and functions for safe removal.
Simplify and clean code
Apply systematic code refactoring with small steps, clear boundaries, and proven techniques. Use when improving existing code, reducing technical debt, cleaning up legacy code, or when user mentions refactoring, code cleanup, or code improvement.
Remove AI-style code slop from a branch by reviewing diffs, deleting inconsistent defensive noise, and preserving behavior and local style.
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.
Finds unused dependencies, files, and exports in JS/TS projects. Use when cleaning up dead code, removing stale packages from package.json, or identifying unreferenced exports.
Knip finds unused files, dependencies, exports, and types in JavaScript/TypeScript projects. Plugin system for frameworks (React, Next.js, Vite), test runners (Vitest, Jest), and build tools. Use when cleaning up codebases, optimizing bundle size, or enforcing strict dependency hygiene in CI.
Aggressively clean up a codebase by removing AI slop, dead code, weak types, defensive over-engineering, duplication, and legacy cruft. Orchestrates 8 specialized subagents in parallel to deduplicate code, consolidate types, kill unused code, untangle circular dependencies, strengthen weak types, remove unnecessary try/catch, delete deprecated/legacy paths, and strip unhelpful comments. Use when the user asks to 'clean up the codebase', 'remove slop', 'improve code quality', 'remove dead code', 'kill AI slop', 'tighten types', 'remove legacy code', 'deduplicate code', 'DRY this up', 'untangle dependencies', or wants a thorough code quality pass. Also use when the user mentions code smells, technical debt cleanup, or refactoring for clarity — even if they don't use the word 'slop'.
Review changed code for reuse, quality, and efficiency, then fix any issues found.
Analyze and transform messy, prototype, overgrown, slop-prone, or hard-to-maintain software repositories into maintainable product-shaped codebases while preserving existing product behavior. Use when the user asks to antislop a codebase, clean up a messy repo, run a maintainability migration, write a refactor plan, modernize structure, improve TypeScript/type boundaries, harden tests, reduce large files, clean architecture, coordinate subagent-driven refactors, or produce a final migration audit/report/microsite. Do not use for broader production-readiness specialties such as security audits, observability/logging programs, compliance hardening, SRE/runbook work, or reliability engineering unless the user explicitly scopes those as part of the maintainability refactor.
Clean up code, remove dead code, and optimize project structure. Use when user wants to clean codebase, remove unused code, or optimize imports.
Corrective cleanup of AI-generated code — removes LLM-specific patterns while preserving behavior. Use when the user says "clean up", "deslop", "slop", "clean AI code", or when you spot LLM-generated code smells after any generation session.