From great-code
Use when evaluating code clarity, questioning abstractions, or investigating overengineering concerns.
How this skill is triggered — by the user, by Claude, or both
Slash command
/great-code:simplicity-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill synthesizes three perspectives on simplicity in software:
This skill synthesizes three perspectives on simplicity in software:
The core synthesis: good code is simple (few entanglements between concepts) and clear (the reader reconstructs the author's intent quickly). Simplicity is structural; clarity is narrative. Both are required.
See references/heuristics.md for evaluation dimensions, default heuristics, a simplicity failure catalog, simplification moves, and pitfalls.
Structure your output as follows:
## Simplicity Judgment
One paragraph: overall assessment. Is the code simpler than, equal to, or more complex than the problem it solves? State who the judgment applies to (new maintainer, domain expert, original author) and under what change model.
## Complexity Sources (ranked)
| # | Location | Type | Essential/Accidental | Mental Hops | Description |
|---|----------|------|---------------------|-------------|-------------|
| 1 | file:L10-25 | Mixed abstraction levels | Accidental | 3 | ... |
## Suspect Abstractions
| Abstraction | Motivation | Fitness | Recommendation |
|-------------|-----------|---------|----------------|
| ConfigFactory | Speculative | Over-abstract | Inline; extract only if second use appears |
## Proposed Moves
For each move:
### Move N: <title>
- **Finding(s)**: #1, #2
- **Move type**: from catalog
- **Before**: code sketch
- **After**: code sketch
- **Risk**: low/medium/high — explanation
## Counterarguments
For each major recommendation, the strongest defense of the current design and why that defense is or is not sufficient.
## Assumptions & Limits
What context is missing, what assumptions were made, and under what conditions the recommendation would change.
## Risk Notes
Any cross-cutting concerns, cascading changes, or tradeoffs the developer should weigh.
Before marking the review as complete, confirm:
npx claudepluginhub eliias/skills --plugin great-codeAnalyzes and simplifies existing implementations to reduce complexity, improve maintainability, and enhance scalability. Use when users ask to simplify code, reduce complexity, refactor for readability, or reduce technical debt.
Runs an unusually strict maintainability review focused on abstraction quality, file size limits, and spaghetti-condition growth. Use for deep code quality audits or harsh structural reviews.
Reviews diffs for over-engineering: reinventing stdlib, unneeded deps, speculative abstractions, dead flexibility. One line per finding with suggested replacement. Complements correctness review.