improve-codebase
Installation
SKILL.md
Goal
Make and verify authorized code and data-path changes, prioritizing the strongest supported gain one bounded scope at a time. Preserve supported features and leave clear owners, contracts, tests, and diagnostics. A percentage is a target, not a deletion quota.
Definition of Done
- The revision, requested target, source unit, fixed baseline and exclusions, supported contracts, callers, and candidate scopes are recorded.
- The selected scope has the strongest evidenced gain relative to effort and risk; each authorized change and its verification finish before selecting another.
- Affected consumers preserve success, failure, security, freshness, and recovery behavior; tests retain meaningful detection.
- Claimed code or data-path gains have comparable before/after evidence, without moving cost or code out of the measured scope; lasting contracts and diagnostics reflect the result.
- Quality validation accepts the selected mode; achieved gain, shortfall, tradeoffs, and unverified requirements are explicit. An assessment makes no changes or test runs.
Boundaries
- Production profiling, traffic replay, migrations, deployments, and external-service changes need their own authority. Use bounded isolated evidence within scope and report missing proof or approval instead of silently changing those systems.