v2.15.1

anti-entropy-governance

ganyuanran@ganyuanran⭐ 1.4k stars· last commit 2d ago· 1 open issues

Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

7.2/10
Verified
Oct 12, 2026

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 1.4k on GitHubGitHub ↗

Very popular

🟢ProSkills ScoreAI Verified
7.2/10
📍

Not yet listed on ClawHub or SkillsMP

// README

Aegis

Stop babysitting your agent. Aegis makes your agent plan against your real baseline before it edits, prove completion with fresh evidence, and leave simple tasks alone — you get fewer reworks, safer changes, and less blind trust in "done".

What You Get

Aegis is a method pack that makes AI coding agents work like disciplined engineers — so you don't have to watch them.

  • Fewer reworks. Your agent aligns with your project's real baseline — owners, contracts, boundaries — before touching code. It stops guessing, and so do you.
  • Safer changes. Measured on a frozen held-out A/B benchmark: contract pass rate 61.67% → 93.33%, unsafe outcomes 13.33% → 0%.
  • Proof before "done". Completion claims ship with fresh verification evidence, covered scope, and residual risk. You read evidence, not vibes.
  • No ghost code. Retired fallbacks and old paths are tracked or removed with a retirement trigger — technical debt stops accumulating silently.
  • Simple tasks stay simple. Trivial requests stay on the fast path; ceremony only appears when the task genuinely needs it.
  • UI/UX rules on demand. UI/UX governance carries project design rules, lower user effort, and scoped experience evidence through design, implementation, review, and verification.
  • One method pack, every host. The same discipline works across Codex, Claude Code, OpenCode, Kimi, and other skill-aware hosts.

These numbers are bounded advisory evidence from Aegis 2.7.6 (2026-08-11), not a measurement of this release, a universal-quality claim, or completion authority. See the full benchmark and its limitations.

Quick Install

New here? The fastest start is one prompt to your agent — the full install-and-verify flow is below.

Give this prompt to your AI coding agent:

Read https://github.com/GanyuanRan/Aegis, identify my current AI coding host, and install Aegis globally using the correct host guide. If the host is the official DeepSeek Harness (`dsh`), treat global/minimal installation as native profile-plugin installation with `dsh plugin --profile <profile> add "git+https://github.com/GanyuanRan/Aegis.git"`; do not silently substitute the direct-child compatibility path unless the plugin manager is unavailable and I explicitly approve compatibility mode. Restart or reload the host if needed, then run complete-install verification from the installed Aegis method-pack root. Do not run the doctor command from the target project directory. First locate `<aegis-method-pack-root>`, then run `cd <aegis-method-pack-root> && python scripts/aegis-doctor.py --write-config --json`. Treat the install as complete only if the JSON includes `"ok": true`, `"workspaceSupport": "available"`, and `"configStatus": "configured"`; if the host uses a separate skill discovery directory, also verify it with `--discovery-root <path>`; if the host guide declares a skill directory name prefix, also pass `--discovery-name-prefix <prefix>`. Also complete the selected host guide's native activation and automatic-entry checks; file discovery or a generic doctor result alone is not sufficient when the host provides a plugin, hook, or session-start bootstrap contract.

Measured Agentic Benchmark

A frozen held-out A/B benchmark for Aegis 2.7.6 (2026-08-11) kept the Codex client, prompts, projects, tool policy, and requested the same gpt-5.6-sol / xhigh setting in both arms; only the Aegis projection differed. Across 120 valid runs on 20 cases, contract pass rate was 61.67% → 93.33% (+31.67 pp) and unsafe outcomes were 13.33% → 0%. The 95% case-cluster interval was +15.00 pp to +50.00 pp. This is bounded advisory evidence; review was arm-hidden technical review, not independent human review, and host events did not return the observed model identity.

Aegis agentic benchmark: with and without Aegis

Sanitized JSON · English table · 中文表格 · Methodology

A newer matrix-v7 standard snapshot for Aegis 2.10.8 covers 22 cases with one observation per arm and case. It uses a different run profile from the extended snapshot above and does not measure the changes in this release.

Try Aegis Methods in a Coding Runtime

Autoloom is our AI coding desktop client. It brings Aegis's change necessity analysis, complexity governance, and delivery review into development execution, helping you spend less time repeating instruc

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/anti-entropy-governance/SKILL.md7.8 KBupstream ↗
    ---
    name: anti-entropy-governance
    description: "Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation."
    ---
    
    # 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:
    
    - pure additive feature work with no retirement decision
    - tiny wording edits
    - simple status or read-only Q&A
    - normal bug fixes that do not involve owner collapse, fallback cleanup, or
      deletion choice
    
    ## Auto-Compose Boundary
    
    This skill should be composed by other owners. It should not become a new
    global hot-path entry.
    
    Prefer composition from:
    
    - `brainstorming` for approach selection involving retirement or persistence risk
    - `writing-plans` for plans that delete old paths or touch schema / migration /
      persistence
    - `systematic-debugging` when the tempting fix is fallback growth or
      delete-vs-retain
    - `verification-before-completion` for cleanup / retirement / compatibility /
      migration closeout
    
    Load automatically when the task touches owner collapse, fallback removal, or schema/persistence/source-of-truth boundaries. Automatic loading identifies and advises only; destructive execution still requires explicit scoped user confirmation.
    
    ## Core Principle
    
    Default to reducing internal entropy, not preserving internal history.
    
    Retirement is responsibility-scoped before it is carrier-scoped. Name the
    obsolete or duplicated authority first. If the same carrier has a separately
    evidenced legitimate role, remove the invalid responsibility and keep only
    that role-scoped capability; this is not a compatibility exception. Apply
    `delete-first` to the carrier once no legitimate responsibility remains.
    Unknown consumers alone still do not justify retaining an internal carrier.
    
    Use this rule:
    
    - internal code retirement -> `delete-first`
    - external compatibility boundary -> `compat-exception` with active dependency
      evidence; `confirmation-first` when distribution is proven but consumers
      cannot be observed
    - persistent-state or irreversible source-of-truth object ->
      `confirmation-first`
    
    Unknown alone neither proves an external dependency nor blocks internal
    `delete-first`. Once distribution is proven, unobservable consumers also do not
    prove deletion safe: inspect read-only. Before editing, require user-authored,
    scoped authorization that explicitly accepts the concrete external risk.
    An informed instruction may already supply it; otherwise disclose the risk
    and request scoped confirmation.
    
    Mentioning, loading, or discussing destructive-action rules never authorizes
    destructive execution. Without explicit scoped user confirmation:
    
    - no irreversible deletion is executed
    - no destructive tool call is made
    - no runnable destructive command is emitted as the next action
    - no broad assent is reinterpreted as deletion approval
    
    ## Deletion Classes
    
    Classify the deletion target first:
    
    - `code-retirement`
      - source code
      - internal triggers
      - duplicate owners
      - stale fallback branches
      - compat-only carriers
      - dead tests/config tied to removed internal behavior
    
    - `contract-carrying code`
      - schema definition files
      - migration files
      - public API contract code
      - host install/discovery code
      - persistence read/write logic
    
    - `live-state mutation surface`
      - code or commands that would mutate live databases, object stores, queues,
        or other persistent state
    
    - `derived-state`
      - rebuildable caches
      - generated indexes
      - temporary exports
      - recomputable artifacts
    
    - `persistent-state`
      - live database tables / columns / rows
      - source-of-truth object storage files
      - user records
      - permission / identity / membership records
      - audit / billing / irreversible business records
      - non-rebuildable queue or event contents
    
    ## Default Path By Class
    
    - `code-retirement` -> `delete-first`
    - `contract-carrying code` -> classify by the Core Principle; internal-only
      retirement uses `delete-first` with high-risk verification
    - `live-state mutation surface` -> inspect and classify; destructive execution
      still requires confirmation when it reaches persistent-state
    - `derived-state` -> verify rebuildability first, then decide
    - `persistent-state` -> `confirmation-first`
    
    ## Hard Stops
    
    If the target is `persistent-state` or another irreversible source-of-truth
    object:
    
    - do not execute deletion automatically
    - do not emit a runnable destructive command as the next action
    - do not call a destructive tool
    - do not interpret generic agreement as confirmation
    - ask for explicit scoped user confirmation
    - request backup / rollback / migration note when relevant
    
    Examples that require confirmation:
    
    - `DROP TABLE`
    - `DROP COLUMN`
    - `TRUNCATE`
    - bulk delete of real business data
    - deleting source-of-truth uploaded files
    - deleting permission, identity, audit, billing, or membership records
    - purging non-rebuildable queues or event streams
    
    ## Data Destruction Guard
    
    When `confirmation-first` protects persistent-state or an irreversible
    source-of-truth object, stop normal retirement flow and emit:
    
    ```text
    Data Destruction Guard:
    - Target Class:
    - Exact Target(s):
    - Environment:
    - Why Irreversible:
    - Backup / Rollback Note:
    - Allowed Read-Only Next Steps:
    - Blocked Destructive Steps:
    - Confirmation Required: yes
    - Status: awaiting scoped confirmation
    ```
    
    Only explicit scoped confirmation can continue. Broad assent such as "OK",
    "continue", or "sounds good" is insufficient. If scope changes at all, previous
    confirmation is invalid and fresh confirmation is required.
    
    ## Anti-Entropy Declaration
    
    Before deletion, state:
    
    ```text
    Anti-Entropy Declaration:
    - Deletion Class:
    - Old Path/Object:
    - Invalid Responsibility / Authority:
    - Legitimate Capability Remaining on Carrier:
    - New Canonical Owner:
    - Expected Preserved Behavior:
    - Expected Retired Behavior:
    - External Boundary Touched: no | yes
    - Source-of-Truth Data Risk: none | possible | confirmed
    - User Confirmation Required: no | yes
    ```
    
    For external-unknown code, fill `User Confirmation Required` with `yes` unless
    the user's own instruction already names the concrete external risk, accepts
    its possible breakage, and authorizes the exact retirement scope, or the user
    later gives scoped confirmation after your disclosure. A generic original
    deletion request does not satisfy this slot. Do not infer acceptance from mere
    awareness of external use or from your own risk summary.
    
    If `User Confirmation Required: yes`, stop normal delete-first flow.
    Persistent-state or irreversible targets enter `Data Destruction Guard`;
    external-unknown code stays in the `Retirement Decision` hold below.
    
    ## Retirement Decision
    
    Choose one path only:
    
    ```text
    Retirement Decision:
    - Path: delete-first | compat-exception | confirmation-first
    - Why:
    - Non-edits:
    ```
    
    R
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/ganyuanran-aegis-skills-anti-entropy-governance.md

// REPO STATS

1.4k stars
1 open issues
Last commit: 2d ago