simplify-and-harden-ci

Simplify & Harden CI

Install

gh skill install pskoett/pskoett-skills simplify-and-harden-ci

Fallback using the Agent Skills CLI:

npx skills add pskoett/pskoett-skills/skills/simplify-and-harden-ci

Purpose

Run a CI-only variant of Simplify & Harden in pull requests:

• No code mutation in CI
• Review only changed files
• Emit structured findings
• Optionally block merge based on severity gates

Use simplify-and-harden for interactive/local coding sessions.

Context Limitation (Important)

CI agents do not have the same peak implementation context as the coding agent that wrote the change. Treat CI findings as structured review signals, not as full intent-aware rewrites.

Implications:

• Prefer scan/report and merge gating
• Do not auto-apply code changes in CI
• Escalate ambiguous findings to interactive review

Prerequisites

1. GitHub Actions enabled for the repository
2. GitHub CLI authenticated (gh auth status)
3. gh-aw installed locally for authoring/validation:

gh extension install

4. In GitHub Actions jobs, install the CLI with:

CI Contract

The CI skill must enforce:

1. Scope lock: review only files changed in the PR
2. Headless execution: report findings, do not apply patches/refactors
3. Structured output: emit simplify_and_harden summary payload
4. Gate policy:
   • critical: fail check when critical harden findings exist
   • advisory (optional): fail check when advisory findings are configured to block

Authoring Workflow (gh-aw)

Example-only template lives in references/workflow-example.md. Keep it outside .github/workflows until you explicitly want automation enabled.

When ready to enable:

1. Copy references/workflow-example.md template block into .github/workflows/simplify-and-harden-ci.md. (The .md extension is intentional: gh-aw workflows are markdown files that gh aw compile compiles into the .lock.yml files GitHub Actions actually runs. This is not a standard hand-written Actions YAML workflow.)
2. Compile and validate workflow:

3. Trigger and push workflow changes:

4. Check status/logs in GitHub Actions and ensure PR feedback is posted.

Prompt Template (CI)

Use this prompt body in your gh-aw workflow:

Recommended Outputs

1. PR comment with concise findings and severity ordering
2. Check run summary with pass/fail reason
3. Machine-readable YAML artifact for downstream automation

Integration with Self-Improvement

Forward simplify_and_harden.learning_loop.candidates into .learnings/LEARNINGS.md via the self-improvement workflow so recurrent patterns can be promoted into durable agent context rules.