ci-fix_skill

This skill helps you diagnose and fix GitHub Actions CI failures using gh, enabling quick, minimal-diff patches and verified reruns.
  • JavaScript

105

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill jmerta/codex-skills --skill ci-fix

  • SKILL.md3.0 KB

Overview

This skill fixes failing GitHub Actions CI using the GitHub CLI (gh). It inspects failing runs and logs, identifies the smallest safe root cause, applies minimal patches to code or workflows, reruns jobs, and summarizes verification and risks. The goal is to get CI green quickly with reviewable diffs and minimal permission changes.

How this skill works

The skill uses gh to locate failing runs (by run ID, PR, or branch), fetch verbose logs and artifacts, and isolate failing jobs and steps. It applies a diagnostic checklist to pick the smallest durable fix (code/test/config first, then workflow plumbing, then rerun for flakes), makes targeted edits, and re-runs the specific failed jobs with gh commands to verify the fix. Finally it produces a concise deliverable summary for the PR or issue.

When to use it

  • A GitHub Actions workflow or PR build is failing and you need a quick, reviewable fix.
  • You need to diagnose intermittent failures and determine if they’re flakiness or real bugs.
  • You want to rerun only failed jobs or steps without triggering full pipelines.
  • You must patch workflow YAML or tests while keeping diffs minimal and permission changes explicit.

Best practices

  • Confirm gh is installed and authenticated; add -R OWNER/REPO when working outside repo context.
  • Prefer deterministic code/config fixes over workflow permission broadening or run-level hacks.
  • Limit changes to the failing job/step and document any security-sensitive edits.
  • Avoid pull_request_target or changes that expose secrets to untrusted fork code unless explicitly approved.
  • Rerun only failed jobs (--failed) or specific jobs by databaseId to minimize noise.

Example use cases

  • A unit test regressed on a branch — inspect failing job logs, fix test or code, rerun the job, confirm green.
  • A flaky integration test — identify transient failure, add retry or stabilize environment, rerun failed job.
  • Workflow permission error — adjust least-privilege permissions for a single job and document risk.
  • Missing artifact or cache issue — download artifacts, repair cache keys or restore missing files, rerun workflow.

FAQ

Use gh run list with --status failure and optional --branch or -w workflow. If you have a URL, extract the run ID from .../actions/runs/<id>.

How do I rerun only the failures?

Run gh run rerun <id> --failed. To rerun a specific job, get its databaseId from gh run view <id> --json jobs and rerun accordingly or re-trigger the workflow for a branch/ref.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational