
When you're cleaning up legacy code and need to decide whether to delete old paths, keep compatibility shims, or stop for explicit approval, this skill enforces a clear hierarchy: internal code gets deleted first by default, proven external dependencies get compatibility exceptions only with evidence, and anything touching persistent state or irreversible data requires scoped user confirmation before execution. It's designed to be composed by other skills like brainstorming or writing-plans rather than called directly. The core tension it resolves is whether your next move should reduce entropy by removing dead code or whether you're about to accidentally break a real dependency or destroy live data. Think of it as a deletion safety referee that knows the difference between retiring a stale fallback branch and dropping a production database table.
$ npx -y skills add ganyuanran/aegis --skill anti-entropy-governance --agent claude-codeInstalls into .claude/skills of the current project.
Use this skill when the task is not merely "change code" but "remove old paths safely without growing entropy".
This skill chooses between:
delete-first for internal code retirementcompat-exception for proven external dependency boundariesconfirmation-first for irreversible state or an external contract whose
distributed consumers cannot be observedIt does not replace brainstorming, writing-plans,
systematic-debugging, or verification-before-completion. It is a narrow
governance owner for retirement, fallback collapse, duplicate-owner cleanup,
and deletion safety.
Use when any of these are true:
Do not use for:
Sponsors