Anti Entropy Governance

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.

GitHub stars: 492
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add ganyuanran/aegis --skill anti-entropy-governance --agent claude-code

Installs into .claude/skills of the current project.

Files

Anti-Entropy

Overview

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 retirement
compat-exception for proven external dependency boundaries
confirmation-first for irreversible state or an external contract whose distributed consumers cannot be observed

It 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.

When to Use

Use when any of these are true:

old logic, duplicate owners, or stale fallbacks should be retired
a candidate fix is "delete old path" vs "add another fallback"
internal keyword / phrase / trigger logic is being replaced by structured logic
a new canonical owner exists and the old owner may still carry real behavior
a cleanup, migration, or deprecation task touches schema, persistence, source-of-truth, or external compatibility boundaries
the task risks confusing code retirement with live data deletion

Do not use for:

SKILL.md on GitHub