skills/self-improvement-ci/SKILL.md
CI-only self-improvement workflow using gh-aw (GitHub Agentic Workflows). Captures recurring failure patterns and quality signals from pull request checks, emits structured learning candidates, and proposes durable prevention rules without interactive prompts. Use when: you want automated learning capture in CI/headless pipelines.
npx skillsauth add pskoett/pskoett-ai-skills self-improvement-ciInstall 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.
gh skill install pskoett/pskoett-skills self-improvement-ci
Fallback using the Agent Skills CLI:
npx skills add pskoett/pskoett-skills/skills/self-improvement-ci
Run self-improvement in CI without interactive chat loops:
simplify-and-harden-cipattern_keyUse self-improvement for interactive/local sessions.
CI agents do not have peak task context from the original implementation session. Use this skill to aggregate recurring patterns across runs, not to infer nuanced one-off intent.
Implications:
pattern_key recurrence signals over single-run conclusionsgh auth status)gh-aw installed for authoring/validation:gh extension install github/gh-aw
The CI skill must:
self_improvement_ci:
source:
pr_number: 123
commit_sha: "abc123"
candidates:
- pattern_key: "harden.input_validation"
source: "simplify-and-harden-ci"
recurrence_count: 3
first_seen: "2026-02-01"
last_seen: "2026-02-20"
severity: "high"
suggested_rule: "Validate and bound-check external inputs before use."
promotion_ready: true
summary:
candidates_total: 4
promotion_ready_total: 1
followup_required: true
pattern_keyrecurrence_count >= 3>= 2 distinct tasks/runsCLAUDE.mdAGENTS.md.github/copilot-instructions.mdSOUL.md / TOOLS.md when using openclaw workspace memoryExample-only templates live in references/workflow-example.md.
Keep examples outside .github/workflows until you explicitly decide to enable CI automation.
When ready:
.github/workflows/self-improvement-ci.mdgh aw compile --validate --strict
gh aw run self-improvement-ci --push
simplify-and-harden-ci to ingest
simplify_and_harden.learning_loop.candidatesself-improvement memory workflow for durable prevention rulestools
Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a `HEAL-` entry to `.learnings/HEALS.md` with proof. Use whenever a command, test, build, or lint fails or exits non-zero; on missing tooling, dependency/lockfile mismatch, wrong runtime version, venv or permission errors, port conflicts, dirty git state, or a missing `.env`; when the agent needs a helper or one-off script that doesn't exist yet; when an external API, tool, or MCP errors or rate-limits; or when a test flakes. Search `HEALS.md` by `Pattern-Key` first — most heals are recurrences, so increment `Recurrence-Count` instead of duplicating. Verify is mandatory: mark `pending-verify` honestly if sandboxed, `abandoned` if the fix can't be made to work. Pairs with `self-improvement` (which promotes recurring heals to durable memory) but owns the verify-before-persist discipline self-improvement doesn't.
development
Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Use this skill whenever the user asks to orchestrate agents, create or steer worker sessions, run a workflow-like effort, fan out audits/research/migrations, coordinate parallel implementation streams, monitor other project sessions, or compare this control-session pattern to Claude Code dynamic workflows. This skill is especially relevant when the current session can spawn persistent project sessions and those sessions can spawn their own subagents, creating a two-level orchestration hierarchy.
tools
Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a `HEAL-` entry to `.learnings/HEALS.md` with proof. Use whenever a command, test, build, or lint fails or exits non-zero; on missing tooling, dependency/lockfile mismatch, wrong runtime version, venv or permission errors, port conflicts, dirty git state, or a missing `.env`; when the agent needs a helper or one-off script that doesn't exist yet; when an external API, tool, or MCP errors or rate-limits; or when a test flakes. Search `HEALS.md` by `Pattern-Key` first — most heals are recurrences, so increment `Recurrence-Count` instead of duplicating. Verify is mandatory: mark `pending-verify` honestly if sandboxed, `abandoned` if the fix can't be made to work. Pairs with `self-improvement` (which promotes recurring heals to durable memory) but owns the verify-before-persist discipline self-improvement doesn't.
development
Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Use this skill whenever the user asks to orchestrate agents, create or steer worker sessions, run a workflow-like effort, fan out audits/research/migrations, coordinate parallel implementation streams, monitor other project sessions, or compare this control-session pattern to Claude Code dynamic workflows. This skill is especially relevant when the current session can spawn persistent project sessions and those sessions can spawn their own subagents, creating a two-level orchestration hierarchy.