Github Fix Ci
Overview
Use this skill to move failed CI checks from symptoms to verified root-cause fixes without bypassing quality gates.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- CI failure taxonomy:
references/ci-failure-taxonomy.md
Templates And Assets
- Failure triage template:
assets/ci-failure-triage-template.md
Inputs To Gather
- PR identifier or current-branch PR context.
ghauthentication with required scopes.- Failed check list, run URLs, and logs.
- Current branch changes and local reproducibility constraints.
Deliverables
- Root-cause summary with evidence links.
- Approved fix plan with minimal change scope.
- Verification evidence (local + GitHub checks).
- Explicit blocker note when full green is not yet possible.
Workflow
- Resolve target PR and gather failures with
scripts/inspect_pr_checks.py. - Record triage in
assets/ci-failure-triage-template.md. - Classify root cause with
references/ci-failure-taxonomy.md. - Propose remediation plan and wait for approval before edits.
- Implement minimal fix and re-run relevant checks.
Scripts
- Run failure inspection:
python3 scripts/inspect_pr_checks.py --repo . --pr <number>
- JSON output for automation:
python3 scripts/inspect_pr_checks.py --repo . --pr <number> --json
- Partial log fetch failures are reported as
snippet_errorwhile processing continues for other checks.
Quality Standard
- Diagnosis includes check name, run URL, and concrete failing evidence.
- Fix scope is directly tied to identified root cause.
- Verification mirrors failing CI surface as closely as practical.
- Remaining blockers are explicit, owned, and time-bounded.
Failure Conditions
- Stop when
ghauthentication or permissions are insufficient. - Stop when root cause cannot be evidenced from logs or reproduction.
- Escalate when failures originate outside GitHub Actions and logs are unavailable.