fix-ci

Diagnose and fix failing GitHub Actions and Google Cloud Build CI checks on pull requests.

2|Updated Sep 25, 2011
One-click install
npx skills add https://github.com/pokutuna/dotfiles --skill fix-ci-pokutuna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-ci
Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/fix-ci
Command: npx skills add https://github.com/pokutuna/dotfiles --skill fix-ci-pokutuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a pull request's CI fails, developers must manually dig through GitHub Actions or Google Cloud Build logs to find the root cause. This Skill automates that investigation: it checks PR CI status, retrieves failure logs from either platform, analyzes the errors, and applies minimal fixes without breaking the PR's intent. ## Core Features & Use Cases - CI Status Inspection: Runs gh pr checks to identify failing jobs on the current branch's PR or a specified PR number/URL. - Dual Platform Support: Retrieves failure logs from GitHub Actions via gh run view --log-failed and from Google Cloud Build via gcloud builds describe and gcloud builds log, including project number to project ID resolution. - Wait Mode: Accepts a wait argument to watch in-progress CI runs with gh pr checks --watch before starting the fix flow, with a 10-minute timeout safeguard. - Use Case: You push a branch, CI fails on Cloud Build, and you ask the assistant to investigate. It extracts the build ID from the check URL, pulls the logs, identifies a failing test, checks out the PR branch, applies a minimal fix, and verifies it locally. ## Quick Start Ask the assistant to check the CI status of the current pull request, analyze any failures, and fix them without pushing.

Frequently Asked Questions about fix-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check why CI failed on a GitHub pull request?

Run gh pr checks to list check statuses, then filter failures with --json name,state,bucket. For GitHub Actions failures, use gh run view <run_id> --log-failed to retrieve the failing job logs directly.

How do I get Google Cloud Build logs for a failed PR check?

Extract the build ID from the console.cloud.google.com/cloud-build/builds URL in the gh pr checks output. Resolve the project number to a project ID with gcloud projects list, then run gcloud builds log <build_id> --project=<project_id>.

Can I wait for a running CI check to finish before analyzing failures?

Yes, pass the wait argument to launch gh pr checks --watch --fail-fast in the background. The workflow monitors completion and proceeds to failure analysis, timing out after 10 minutes if the run does not finish.

Does this workflow push fixes to the pull request automatically?

No, it never runs git push. It checks out the PR branch with gh pr checkout, applies minimal fixes, and optionally verifies them locally, leaving the push decision to the user.

What are the limitations of automated CI failure fixing?

Fixes are limited to issues reproducible from failure logs, and CI-environment-specific problems may not be resolvable locally. The workflow reports such remaining issues instead of attempting speculative changes.