code-quality

Rank the functions in a Python or JavaScript/TypeScript tree by cyclomatic complexity, length and nesting depth with a bundled script, then explain which ones to simplify and how. Use when asked "which code is most complex?", where to start a cleanup, to set or enforce a complexity threshold in CI, or to measure a refactor before and after. Not for runtime performance (use perf-profile-reader) and not a substitute for reading the code.

Shrink a codebase safely: a bundled script lists probably-unused functions, classes, unused methods and exports in a Python or JavaScript/TypeScript tree, each candidate is confirmed by searching for dynamic use, and the skill proposes a safe order to remove them. Use when asked to find dead or unused code, "what can be deleted safely", or to prepare a cleanup before a refactor. Not for unused imports or variables inside a function (a linter does that) and not for unused dependencies in package manifests.

Review how a codebase or change handles failures: swallowed exceptions, missing timeouts and retries, errors without context, leaking internals to users, and inconsistent error types across layers; then propose a consistent policy with code examples. Use when asked to review error handling, when a bug report says "it failed silently", or when designing the error strategy for a service or library. Not for logging configuration alone and not for incident response (use postmortem-writer).

Audit names in a module or diff for clarity, consistency with project conventions and lies (names that no longer match behaviour), then propose renames with a migration path for public ones. Use when asked "are these names clear?", to review naming in a PR, or to agree conventions for a new codebase. Not for formatting or choosing a product name.

Produce a step-by-step refactoring plan for a module, package or feature, with a behaviour-preserving sequence of small commits, the tests that guard each step, and a rollback point. Use when asked to refactor, restructure, split a large file, untangle dependencies, or "clean up" code without changing behaviour. Not for feature work or bug fixes; those change behaviour and belong in a normal change.

Review a pull request, diff or branch against a fixed checklist (correctness, tests, error handling, security, performance, readability, compatibility) and produce findings with file and line references and a verdict. Use when asked to review code, a PR, a diff or "look over my changes" before merging. Not for style-only nitpicks a formatter handles, and not for a full security audit (use the security-basics skills for that).

Find the source modules that have no tests and prioritise which to cover first by risk: a bundled script maps modules to their tests by naming convention and imports and shows what is missing. Use when asked "what is untested?", where to add tests first, or to check that a change comes with tests. Not for line coverage; it works at module level without running anything (use coverage.py, c8 or go test -cover for that).

Measure how much of a Python or TypeScript codebase is type-annotated with a bundled script (parameters and return values per function, explicit any counts), find the least-typed files, and plan a gradual typing rollout with a CI threshold. Use when asked "how well typed is this code?", where to add types first, or to enforce typing on new code. Not for finding type errors; it measures annotations only (run mypy, pyright or tsc for that).