ADG Repair Loop Skill

To enforce a pre-edit gate for code repair sessions, you can use a 4-question litmus test based on ADG artifacts. This process identifies the correct ADG cluster, root module, scoped tests, and blast radius justifications before allowing any code modifications.

An ADG cluster is a structural grouping identified within ADG JSON artifacts used to guide code modifications. It helps pinpoint the exact root module and determine the blast radius of changes, ensuring deterministic and auditable code repair discipline.

You validate blast radius and scoped tests by answering a 4-question litmus test using ADG artifacts. This requires identifying the specific ADG cluster, gathering precise test IDs, and justifying the blast radius before making any code changes.

Yes, you need existing ADG artifacts in JSON format to run the repair discipline litmus test. If artifacts are missing or outdated, the skill provides specific commands for rebuilding them so you can accurately identify the root module and blast radius.

The best way to ensure deterministic and auditable code modifications is to enforce a strict pre-edit gate using ADG artifacts. This involves validating the ADG cluster, root module, and scoped tests, then executing those scoped tests after rebuilding artifacts.

Scoped tests fail when modifying root modules without ADG validation because the blast radius and cluster dependencies are not properly justified. Enforcing a pre-edit gate with ADG artifacts ensures you pinpoint the exact root module and gather precise test IDs before changes.