All skills
code-clarity-maintainability
FoundationJIT onlyanalysis-agent/task-agent/review-agent: use when changed flow, naming, or navigation hides obligations; skip placement, API-contract, language, or performance decisions.
- Group
- Engineering workflow
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- changed code clarity main flow exceptional path guard extraction inline nesting evaluation order short-circuit cleanup cancellation side-effect visibility
- condition naming semantic state unit authority failure meaning comment contract regression test readability
- split merge helper chain navigation entry point owner public test effect boundary next-change deletion path
Do not use when
Anti-triggers — as binding as the triggers above
- the unresolved decision is file object module signature or public-contract placement
- the task is behavior-preserving movement language semantics or runtime performance with no remaining code-clarity decision
Required inputs
What must be supplied before this skill can decide anything
- changed entry point and affected terminal outcomes
- current source and tests for evaluation cleanup and effect order
- owner and navigation evidence for any split merge extraction or inline
Output contract
What this skill owes the next role
- code-clarity decision with obscured path preserved obligations selected move rejected simplification public-behavior proof evidence limits and residual risk
Escalation signals
When this skill must hand the decision back
- A clarity move can hide cleanup cancellation authority side effects public behavior or the next-change and deletion path
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | A code-clarity choice between guard extraction inline split merge or direct flow remains unresolved | The code-clarity change is a direct naming or comment correction with no competing flow or navigation move | AnalysisTaskReview |
| checklist.mddecision-checklist | A code-clarity change spans exceptional paths, cleanup, side effects, or split-merge navigation and requires obligation-to-outcome traceability | The code-clarity obligation and affected terminal outcomes are explicit in the changed path | AnalysisTaskReview |