github-fix-ci
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.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9