
Ci Fix
When your GitHub Actions go red, this skill pulls the logs, identifies what broke, implements a minimal fix, and pushes it to a dedicated branch without opening a PR. It walks through the full workflow: locating the failing run via gh CLI, extracting failure logs, diagnosing common patterns like build errors or flaky tests, and verifying the fix works. The approach is practical and safety-conscious, warning against broadening workflow permissions just to make tests pass and preferring deterministic code fixes over workflow plumbing. It's designed for the common case where you need CI green again but don't want to guess at solutions or manually hunt through log output across multiple failed jobs.
- skills.sh installs
- 207
- GitHub stars
- 824
- last updated
- Aug 21, 2026
Install
$ npx -y skills add warpdotdev/oz-skills --skill ci-fix --agent claude-codeInstalls into .claude/skills of the current project.
Files
CI Fix
Diagnose CI failures and implement fixes with minimal, targeted diffs. Pushes fixes to a dedicated branch without creating PRs.
Prerequisites
Verify GitHub CLI authentication before proceeding:
gh auth status
If not authenticated, instruct the user to run gh auth login first.
Workflow
1. Locate the Failing Run
Determine the failing workflow run. If working on a PR branch:
gh pr view --json statusCheckRollup --jq '.statusCheckRollup[] | select(.conclusion == "FAILURE")'
If working from a branch or run ID:
gh run list --branch <branch> --status failure --limit 5
gh run view <run-id> --verbose
2. Extract Failure Logs
Pull logs from failed steps to identify the root cause:
gh run view <run-id> --log-failed
For deeper inspection:
gh run view <run-id> --log --job <job-id>
gh run download <run-id> -D .artifacts/<run-id>
3. Identify Root Cause
Analyze logs for common failure patterns:
Sponsors
Details
- Repository
- github.com/warpdotdev/oz-skills
- Categories
- DevOps & CI/CD, Git & Pull Requests, Debugging, Automation & Workflows
- First seen
- Jun 3, 2026