skills.rest
nearmap
nearmapOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ci

Triage, diagnose, and fix the current branch's CI failures until green.

1|1|Updated Jul 23, 2026
Search Tags:#pull request#github actions#diagnosis#polling#build failures#triage#CI
One-click install
npx skills add https://github.com/nearmap/shipyard --skill ci-nearmap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/nearmap/shipyard/tree/main/skills/ci
Command: npx skills add https://github.com/nearmap/shipyard --skill ci-nearmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Watching CI runs, paging through massive failure logs, and distinguishing real branch bugs from flakes or inherited main breakage consumes developer time and floods context with noise. This Skill automates that triage loop so the current branch's CI reaches green without manual log digging. ## Core Features & Use Cases - Current-head run detection: Finds the checks that actually cover the current HEAD SHA, waits on pending runs with a shared background poller, and never mistakes a stale green run for current coverage. - Context-safe diagnosis: Delegates large failing logs to a sweep subagent that returns failing jobs, decisive root-cause lines, and implicated code pointers instead of raw logs. - Report or fix modes: Reports the failing job, real error, cause, and concrete fix, or in fix mode applies the fix, pushes, and re-watches the new HEAD until green. - Use Case: After pushing a PR, ask the agent to check CI; it waits for the matrix to finish, identifies that a test failure is a branch bug rather than a flake, applies the fix, pushes, and confirms the new HEAD is green. ## Quick Start Run the ci skill in fix mode to diagnose this branch's failing CI and push fixes until the current HEAD is green.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I diagnose failing CI checks on my pull request?▼

Detect the branch and current HEAD SHA, find the checks covering that SHA, then analyze failing logs with a sweep subagent that returns failing jobs, root-cause lines, and code pointers. Compare against the latest main job to rule out pre-existing breakage.

How to automatically fix CI failures and re-run checks?▼

Use fix mode: apply the diagnosed fix, run local reproducer checks, push the commit, and re-watch the new HEAD until it is green. The skill reports status as green, fixably-red, or blocked with the covered SHA.

How can I tell if a CI failure is a flake or a real bug?▼

Verify the corresponding latest main job before concluding anything. Distinguish branch bugs, inherited main breakage, flakes, resource limits, dependency drift, and infra or network failures based on that comparison.

Why does CI show green but my latest commit was never tested?▼

An older green run can be mistaken for current-head coverage. Always match checks to the current HEAD SHA and pass the expected head to the poller so a stale or empty check set cannot read as green.

Can this skill merge my PR after CI passes?▼

No, the skill never merges. It only reports CI status or pushes fixes until the current HEAD is green, leaving the merge decision entirely to you.

Related Skills

Explore More Software Engineering Skills→
JSdotNetJSdotNet

push-branch

Push the current git branch to its remote and report the result without opening a pull request.

Community
Intermediate
fallow-rsfallow-rs
4.4k

ship

Merges reviewed Fallow work to main with pre-push checks and CI monitoring.

Official
Intermediate
matteingmatteing
56

ci-preflight

Run the full CI suite locally to verify Elixir and TypeScript checks before pushing.

Community
Intermediate
vadimcomanescuvadimcomanescu
24

gh-fix-ci

Inspect failing GitHub Actions checks and summarize actionable failure logs.

Community
Intermediate