ci-fix-and-verify

Diagnoses and fixes failing GitHub PR checks until all CI passes.

218|11|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/baseballyama/rsvelte --skill ci-fix-and-verify-baseballyama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-fix-and-verify
Source: https://github.com/baseballyama/rsvelte/tree/main/.claude/skills/ci-fix-and-verify
Command: npx skills add https://github.com/baseballyama/rsvelte --skill ci-fix-and-verify-baseballyama

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually debugging failing CI checks on a pull request is slow and repetitive: you read logs, reproduce failures locally, push a fix, and wait again. This Skill automates that loop by detecting failed checks, reproducing them locally, committing fixes, and polling until every check passes. ## Core Features & Use Cases - Automated failure diagnosis: Reads failed GitHub Actions logs via gh run view and maps each failure type (fmt, clippy, build, tests, fixtures, docs) to the exact local reproduction command. - Fix-push-wait cycle: Commits fixes with Conventional Commits, pushes, and polls CI status with a dedicated wait-ci.sh script that reports ALL_PASSED, FAILED, TIMEOUT, or API_ERROR. - Bounded retry loop: Repeats the fix cycle up to 5 times and reports status to the user if the limit is exceeded, never bypassing pre-commit hooks. - Use Case: A Rust project PR fails clippy and test checks. Invoke the Skill with the PR number; it reproduces the failures with cargo clippy and cargo test, applies fixes, pushes, and waits until all checks turn green. ## Quick Start Ask the assistant to fix the failing CI on pull request 42 and keep iterating until every check passes.

Frequently Asked Questions about ci-fix-and-verify

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

FAQPage Schema
How do I automatically fix failing CI checks on a GitHub pull request?▼

Invoke the Skill with the PR number, or let it detect the PR from the current branch. It reads failed check logs with gh run view, reproduces each failure locally, commits a fix, pushes, and polls until all checks pass.

How to reproduce GitHub Actions failures locally for a Rust project?▼

The Skill maps each failure type to a local command: cargo fmt --all for formatting, cargo clippy --all-targets --all-features -- -D warnings for lints, cargo build --all-targets for builds, and cargo test --release --test <suite> for individual failing tests.

Does this work if I don't provide a pull request number?▼

Yes. When no PR number is given, the Skill detects the open PR for the current branch using gh pr list --head with the current git branch name, then proceeds with the same fix-and-verify cycle.

What happens if CI keeps failing after several fix attempts?▼

The fix cycle is capped at 5 iterations. If checks still fail after that, the Skill stops and reports the current situation to the user instead of looping indefinitely.

How long does the Skill wait for CI checks to complete?▼

The wait-ci.sh script polls every 30 seconds for up to 20 minutes. On timeout it returns TIMEOUT, and the Skill re-checks status with gh pr checks and can extend the wait by running the script again.

Can the Skill bypass pre-commit hooks to push fixes faster?▼

No. The Skill explicitly forbids flags like --no-verify. It runs cargo fmt and cargo clippy before committing so the push matches the pre-commit hook requirements.