Refactor code to reduce cyclomatic complexity so it stays readable, maintainable, and aligned with the long-term vision of the codebase, not just optimized for AI comprehension. Use whenever the user asks to refactor, simplify, clean up, or review code quality; mentions complexity, maintainability, readability, spaghetti code, deeply nested logic, or god functions; or asks to check AI-generated code before merging. Also use proactively after writing any nontrivial function with heavy branching.
Install
KitScout test notes
Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.
Similar tools
rea-tool-design456,474 ★ Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and E
reverse-engineer-anything456,474 ★ Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and b
code-review323,337 ★ Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does th
codebase-design323,337 ★ Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interfac
domain-modeling323,337 ★ Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLO