Agent skill
ci-fix
Fix GitHub Actions CI failures using GitHub CLI (gh): inspect runs/logs, identify root cause, patch workflows/code, rerun jobs, and summarize verification. Use when GitHub Actions CI is failing or needs diagnosis.
Install this agent skill to your Project
npx add-skill https://github.com/jMerta/codex-skills/tree/main/ci-fix
SKILL.md
CI fix (GitHub Actions)
Goal
- Get CI green quickly with minimal, reviewable diffs.
- Use
ghto locate failing runs, inspect logs/artifacts, rerun jobs, and confirm the fix.
Inputs to ask for (if missing)
- Repo (
OWNER/REPO) and whether this is a PR or branch build. - Failing run URL/ID (or PR number / branch name).
- What "green" means (required workflows? allowed flaky reruns?).
- Any constraints (no workflow edits, no permission changes, no force-push, etc.).
Workflow (checklist)
- Confirm
ghcontext- Auth:
gh auth status - Repo:
gh repo view --json nameWithOwner -q .nameWithOwner - If needed, add
-R OWNER/REPOto all commands. - If
ghis not installed or not authenticated, tell the user and ask whether to install/authenticate or proceed by pasting logs/run URLs manually.
- Auth:
- Find the failing run
- If you have a run URL, extract the run ID:
.../actions/runs/<id>. - Otherwise:
- Recent failures:
gh run list --limit 20 --status failure - Branch failures:
gh run list --branch <branch> --limit 20 --status failure - Workflow failures:
gh run list -w <workflow> --limit 20 --status failure
- Recent failures:
- Open in browser:
gh run view <id> --web
- If you have a run URL, extract the run ID:
- Pull the signal from logs
- Job/step overview:
gh run view <id> --verbose - Failed steps only:
gh run view <id> --log-failed - Full log for a job:
gh run view <id> --log --job <job-id> - Download artifacts:
gh run download <id> -D .artifacts/<id>
- Job/step overview:
- Identify root cause (prefer the smallest fix)
- Use
references/ci-failure-playbook.mdfor common patterns and safe fixes. - Prefer: deterministic code/config fix > workflow plumbing fix > rerun flake.
- Use
- Implement the fix (minimal diff)
- Update code/tests/config and/or
.github/workflows/*.yml. - Keep changes scoped to the failing job/step.
- If changing triggers/permissions/secrets, call out risk and get explicit confirmation.
- Update code/tests/config and/or
- Verify in GitHub Actions
- Rerun only failures:
gh run rerun <id> --failed - Rerun a specific job (note: job databaseId):
gh run view <id> --json jobs --jq '.jobs[] | {name,databaseId,conclusion}' - Watch until done:
gh run watch <id> --compact --exit-status - Manually trigger:
gh workflow run <workflow> --ref <branch>
- Rerun only failures:
Safety notes
- Avoid
pull_request_target(and any change that runs untrusted fork code with secrets) unless the user explicitly requests it and understands the security tradeoffs. - Keep workflow
permissions:least-privilege; don’t broaden token access “just to make it pass”.
Deliverable (paste in chat / PR)
- Summary: ...
- Failing run: <link/id> (job/step)
- Root cause: ...
- Fix: ...
- Verification: commands + new run link/id
- Notes/risks: ...
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
vps-checkup
SSH into an Ubuntu VPS (Docker) for a read-only health/security/update report (UFW + fail2ban) and propose fixes; apply updates/restarts only with explicit confirmation. Use when the user wants a read-only VPS health/security check.
dependency-upgrader
Upgrade dependencies for Java/Kotlin (Gradle/Maven) and TypeScript/Node projects with minimal risk: plan the bump, apply changes incrementally, run tests/builds, and document breaking changes. Use when the user asks to bump deps, update frameworks, or address CVEs.
plan-work
Plan work before coding: do repo research, analyze options/risks, and ask clarifying questions before proposing an implementation plan. Use when the user asks for a plan, design/approach, scope breakdown, or implementation steps.
coding-guidelines-gen
Generate nested AGENTS.md coding guidelines per module (monorepo-aware), detect languages/tooling, ask architecture preferences, and set up missing formatters/linters (Spotless for JVM). Use when the user wants module-scoped AGENTS.md coding guidelines or to set up missing formatters/linters.
ui-ux-pro-max
Use when designing, building, or refining frontend UI/UX: layouts, components, visual systems, typography, color, and UX patterns for websites, landing pages, dashboards, and product interfaces. Provides searchable styles, palettes, font pairings, charts, and stack best practices (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind).
regex-builder
Build, test, and explain regular expressions against sample text or files using CLI tools (rg, python) and specific regex flavors. Use when asked to craft, debug, or validate regexes or search patterns.
Didn't find tool you were looking for?