skills/aoa-session-self-repair/SKILL.md
--- name: aoa-session-self-repair scope: core status: scaffold summary: Turn a reviewed diagnosis packet into the smallest honest repair packet with checkpoint posture, rollback markers, health checks, and explicit owner-layer targets instead of silent self-mutation. invocation_mode: explicit-only technique_dependencies: - AOA-T-0082 - AOA-T-0083 --- # aoa-session-self-repair ## Intent Use this skill to author a bounded `REPAIR_PACKET`. The repair packet should be small, explicit, revers
npx skillsauth add 8Dionysus/aoa-skills aoa-session-self-repairInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to author a bounded REPAIR_PACKET.
The repair packet should be small, explicit, reversible where needed, and aligned with checkpoint posture before any important system surface is changed.
Use this skill when:
Do not use this skill when:
REPAIR_PACKET with target owner repo, smallest diff shape, approval need, rollback marker, health check, and improvement-log stubREPAIR_CYCLE_RECEIPT using references/stats-event-envelope.md and
references/repair-cycle-receipt-schema.yamlCORE_SKILL_APPLICATION_RECEIPT using
references/core-skill-application-receipt-schema.yamlREPAIR_CYCLE_RECEIPT when the repair packet or repair-quest handoff closes, keeping the receipt smaller than the packetCORE_SKILL_APPLICATION_RECEIPT
that points back to the bounded repair receipt and records one finished
kernel-skill applicationaoa-agentsaoa-evalsaoa-playbookssupersedes rather than silent overwriteCORE_SKILL_APPLICATION_RECEIPT points to the repair
detail receipt and stays finish-onlyManifest-backed techniques:
8Dionysus/aoa-techniques at 5c6f0496edc3c2e74590baa35627c85fe58ef765 using path techniques/agent-workflows/repair-shape-from-diagnosis/TECHNIQUE.md and sections: Intent, Inputs, Outputs, Core procedure, Validation8Dionysus/aoa-techniques at 5c6f0496edc3c2e74590baa35627c85fe58ef765 using path techniques/agent-workflows/checkpoint-bound-self-repair/TECHNIQUE.md and sections: Outputs, Contracts, Risks, ValidationProject overlays may add:
development
Sanitize private technical material into a public-safe owner-bounded derivative, or resolve authority among authored, generated, runtime, and installed sources. Use for governed incidents, logs, configs, diagnostics, or conflicting source roles. Do not use for ordinary editing, memo/session work, direct publication, or durable-memory authority.
tools
Diagnose a reviewed recurring session/workflow failure, or carry one bounded owner repair through checkpoint, rollback, and real health verification. Use for reviewed contamination, drift, repeated route/tool failure, or an established diagnosis ready for repair. Do not use on live evidence, for vague self-improvement, or to call a proposed or merely executed change verified.
tools
Use only when a literal ref to a closed/reviewed session packet is supplied, to extract, classify, propose promotion or branching, or identify an automation opportunity. Missing, live, or unreviewed evidence must fail closed without inventing a ref. Natural closeout preservation belongs to aoa-memo-writeback. Do not use for generic summaries, progression, direct owner writes, scheduling, mutation, or telemetry authority.
testing
Turn one stable technical truth into bounded evidence through contract, coverage-audit, or property mode. Use to define a named consumer seam, audit what existing checks really constrain, or express a broad invariant after manual cases establish meaning. Compose with aoa-eval when an evaluation surface must first be found or applied. Do not use for undefined behavior, generic test plans, or green checks as whole-system proof.