Agent skill · pskoett
self-healing-ci
CI-only self-healing workflow using gh-aw (GitHub Agentic Workflows) for active runtime recovery on pull requests and scheduled runs. When a CI check fails (test, build, lint, deploy, scan), this skill diagnoses the failure from CI logs, proposes a verified patch as a PR comment or follow-up commit, and commits a HEAL entry to `.learnings/HEALS.md`. Verify-before-persist discipline preserved: a HEAL is only `verified` if a re-run check passes in the same workflow; otherwise it ships as `pending-verify` for human follow-up. Recurrent heal patterns across PRs accumulate `Recurrence-Count` and append a `Handoff` block at ≥3 to flag promotion via self-improvement-ci. Use this skill when: you want headless heal-loop execution in CI/scheduled pipelines, you want recurring failure patterns captured automatically, or you want PRs that surface non-obvious environmental / tooling fixes without human triage. For interactive/local sessions, use `self-healing` instead.
What it needs
About 5k tokens when loaded.
What this skill does
Self-Healing CI CI-only variant of self-healing. Runs the diagnose → patch → verify → file loop headlessly against pull-request and scheduled workflow events. Install Fallback using the Agent Skills CLI: Purpose Run self-healing in CI without interactive chat loops: Inspect failed PR checks (test/build/lint/scan/deploy) and parse logs for root cause Propose a minimal verified patch as a PR comment or follow-up commit Commit a HEAL- entry to .learnings/HEALS.md with verification proof (or pending-verify if the workflow can't re-run the check) Search prior HEAL entries by Pattern-Key before filing new ones — deduplicate recurrences Append a Handoff block at Recurrence-Count >= 3 for promotion via self-improvement-ci Use self-healing for interactive/local sessions. Context Limitation (Important) CI agents do not have peak task context from the original implementation session. The agent is reading CI logs and code, not riding peak context after a focused implementation. Implications: Favor conservative diagnoses — when uncertain, file pending-verify and surface to the PR author Require mandatory verify before claiming verified — re-run the failing check in the same workflow run Never modify project code without an explicit verify pass; propose changes as PR comments unless the workflow is configured for auto-commit Route uncertain or high-impact recommendations to interactive review Prerequisites 1. GitHub Actions enabled for the repository 2. GitHub CLI authenticated in the workflow (gh auth status) 3. gh-aw installed for authoring/validation: 4. .learnings/HEALS.md committed to the repo (or created on first run; see references/workflow-example.md for the bootstrap pattern) CI Contract The CI skill must: 1. Read CI logs, PR diff, and existing .learnings/HEALS.md — nothing else from the PR author's machine 2. Avoid direct code modifications by default — propose via PR comment or label-gated commit 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pskoett/self-healing-ci--304698