ci-failure-batching

Collects all CI check failures on a pull request before fixing them in one push cycle.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill ci-failure-batching-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-failure-batching
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/ci-failure-batching
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill ci-failure-batching-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a CI check fails on a pull request, the natural instinct is to fix it immediately and push. But if multiple checks fail, this creates a serial diagnose-fix-push loop where each failure triggers its own push cycle, wasting CI minutes and review time. This Skill enforces a batching protocol: wait for the full check run to complete, collect every failure, fix them all together, and push once. ## Core Features & Use Cases - Failure Collection Protocol: Uses gh pr checks and gh run view --log-failed to verify all jobs finished and build a complete failure ledger before any fix attempt. - Clustered Fixing: Groups failures by root cause so related issues are resolved in a single changeset verified locally. - Push Discipline: Delegates commit and push to the commit-pr skill, mandating --force-with-lease over blocked bare force pushes and preferring a new fix commit over amending pushed work. - Use Case: A PR fails on formatting, two stale assertions, and an integration test. Instead of six push cycles, you wait for the run to finish, fix all four issues locally, and push once. ## Quick Start When a PR's CI fails, wait for all checks to complete, collect every failure log with gh, fix them all together, and push a single fix commit.

Frequently Asked Questions about ci-failure-batching

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

FAQPage Schema
How do I fix multiple CI failures on a GitHub pull request efficiently?

Wait for the entire check run to complete using gh pr checks, then collect every failed job's logs with gh run view --log-failed. Cluster the failures by root cause, fix them all locally, verify, and push a single fix commit instead of one push per failure.

How to view failed CI job logs with the GitHub CLI?

Run gh pr checks <PR> to list check statuses, then use gh run view <run-id> --log-failed for each failing run to retrieve only the failed step logs. This builds a complete failure ledger before you start fixing anything.

Why should I wait for all CI checks to finish before fixing failures?

Fixing the first failure immediately causes serial diagnose-fix-push cycles, since later jobs may also fail. Waiting lets you fix everything in one changeset, turning N failures into one push cycle instead of N.

Can I force push CI fixes to a pull request branch?

Bare git push --force and -f are blocked by guardrails, but --force-with-lease is allowed because it refuses to overwrite remote work gained since your last fetch. Even so, prefer a normal new fix commit over amending an already-pushed commit.

When should I re-push after fixing batched CI failures?

Only re-push if new failures surface that were not part of the original collected batch. If the same batched failures reappear, the fix was incomplete and should be corrected locally first.