Understand a failing GitHub check

Before you start

You’ll make: The failing check, relevant log evidence, and a proposed fix you can review.

• Codex open in your Git repository.
• GitHub CLI installed and signed into an account with access to the repository.
• An existing pull request with a failing GitHub Actions check.

Run these checks in your terminal before the install prompt.

gh --version
gh auth login
gh auth status

1. Install the skill

Paste into a Codex conversation, not your terminal shell.

$skill-installer gh-fix-ci

Use GitHub’s normal browser sign-in when gh asks. Do not paste an access token into the agent chat.

Open the official source below and review SKILL.md, scripts, and the license. If the skill is missing after installation, start a new session or follow the agent’s reload guidance.

2. Try a small task

Copy this into a new Codex conversation. Replace example filenames with your own non-sensitive files where needed.

$gh-fix-ci Inspect the failing GitHub Actions checks on my current pull request. Explain the cause with log evidence and propose the smallest fix. Wait for my approval before editing, committing, or pushing.

3. Check the result

• The report identifies the actual PR and failing job.
• Its explanation points to the relevant log, rather than guessing.
• Code changes wait for your approval; external CI providers are identified separately.

If something doesn’t work

Repository or PR not found

Open the correct local repository and check gh auth status. Share the public PR URL or number, not credentials.

The failure comes from another CI provider

This skill focuses on GitHub Actions. Follow the external check’s details link and diagnose that service separately.