Reviews recently changed files for code reuse, quality, and efficiency issues via parallel agents, then applies fixes. Use after completing a change.
How this skill is triggered — by the user, by Claude, or both
Slash command
/v1truv1us-ai-eng-system:simplifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is an expanded profile of `code-simplification` that adds multi-agent parallel review. For the canonical simplification workflow, see `skills/code-simplification/SKILL.md`.
This is an expanded profile of code-simplification that adds multi-agent parallel review. For the canonical simplification workflow, see skills/code-simplification/SKILL.md.
git diff --stat| Agent | Focus | Finds |
|---|---|---|
| Code Reuse | Duplication | Repeated logic, extractable functions, copy-paste patterns |
| Quality | Complexity | Dead code, poor naming, deep nesting, missing error handling |
| Efficiency | Performance | Redundant allocations, unnecessary iterations, missing caches |
Pass a focus argument to weight the matching agent higher:
memory efficiencyreadabilityreducing duplicationperformanceerror handlingcode-simplification — Canonical simplification skillcode-review-and-quality — Multi-axis code reviewtext-cleanup — AI verbosity removal (different from code simplification)| Excuse | Counter |
|---|---|
| "The multi-agent review is overkill for small changes" | Small changes can hide duplication and inefficiency. Parallel review catches what single review misses. |
| "I'll skip the efficiency agent, readability is enough" | Performance regressions creep in silently. The efficiency agent catches them before they compound. |
| "Aggregating findings takes too long" | Unaggregated findings lead to conflicting fixes. Deduplicate and prioritize before applying. |
| "I'll simplify test code too" | Test code prioritizes clarity over brevity. Do not simplify tests for the sake of fewer lines. |
| "The confidence score is just a number" | Confidence scores flag areas that need human review. Low confidence means "look closer." |
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
2plugins reuse this skill
First indexed Jul 8, 2026
npx claudepluginhub v1truv1us/ai-eng-system