show-complexity

Installation
SKILL.md

Show complexity

Make complexity visible, explain what requires it, and identify what can be simplified. Borrow show-me's approach: use the smallest visual that explains the point, place evidence beside it, and keep prose brief.

Establish the scope

Use the conversation to identify the target and the decision the user needs to make. For a change, establish the comparison base and include relevant staged, unstaged, and new files. For a proposal, distinguish the proposed design from existing code.

Start with applicable project guidance, package documentation, a file inventory, and entry-point and caller searches. Before judging an abstraction, distinguish production-used APIs, test-only APIs, and apparently unused code. Check registrations and supported external consumers before declaring an entry point unused. For apparent duplicates, establish which implementation production callers use.

Select consequential workflows from that inventory. Trace their callers, state, dependencies, and failure paths, reading the requirements that govern them. Expand discovery only to resolve a named question that could change a classification or recommendation. Follow each suspected burden far enough to identify who owns it and who pays for it.

For a whole project, use a shallow responsibility map to select the areas to inspect. State which areas were sampled and which remain unexamined. Ask a focused question only when an unknown requirement or scope choice would change the assessment.

Proceed when you can name the required behavior, the relevant constraints, and the implementation mechanisms being assessed. Cite file paths and symbols, with line numbers when useful. Treat missing rationale as uncertainty rather than evidence that a mechanism is unnecessary.

Classify the burden

Classify individual rules, relationships, or mechanisms rather than labeling an entire module essential or accidental.

Installs
1
First Seen
Oct 11, 2026