Borrowing it
Nothing to install: this file belongs to warpdotdev/common-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/warpdotdev/common-skills/main/.agents/skills/diagnose-ci-failures/SKILL.mdgit clone --depth 1 https://github.com/warpdotdev/common-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/warpdotdev/common-skills/diagnose-ci-failures)<a href="https://agentmods.dev/skills/warpdotdev/common-skills/diagnose-ci-failures"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/diagnose-ci-failures/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/warpdotdev/common-skills/diagnose-ci-failures"><img src="https://agentmods.dev/badge/skills/warpdotdev/common-skills/diagnose-ci-failures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.00970 |
| Opus 5.5 | $0.00023 | $0.00388 |
| Sonnet 5.5 | $0.00011 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
diagnose-ci-failures scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
diagnose-ci-failures
Programmatically diagnose CI failures for a PR and generate a plan to fix them.
Overview
This skill provides a deterministic workflow to check CI status for a PR, extract failure logs, analyze errors, and create a plan (not code changes) to resolve issues. The output is always a plan document that can be reviewed before execution.
Workflow
1. Verify PR exists for current branch
Get the current branch and check if a PR exists:
# Get current branch
git branch --show-current
# Check for PR
GH_PAGER=cat gh pr view <branch-name> --json number,title,url,state
If no PR exists, inform the user and offer to create one using the create-pr skill.
2. Check CI status
Fetch the status of all CI checks:
GH_PAGER=cat gh pr view <branch-name> --json statusCheckRollup
Parse the output to identify:
- Completed checks vs. in-progress checks
- Successful checks
- Failed checks with their names and details URLs
If CI is still running, inform the user which checks have already failed or passed, highlight the checks that are still running, and suggest waiting for completion before diagnosis.
3. Extract failure logs
For each failed check, pull the logs using the run ID from the status check:
GH_PAGER=cat gh run view <run-id> --log-failed
Focus on extracting:
- Error messages and their locations (file paths, line numbers)
- Compilation errors (unused imports, type mismatches, etc.)
- Linting/clippy errors with specific lint names
- Test failure messages and stack traces
- Build failures and their root causes
4. Categorize errors
Group errors by type:
- Formatting issues:
cargo fmtfailures - Linting issues:
cargo clippywarnings/errors - Compilation errors: Type errors, missing imports, signature mismatches
- Test failures: Failing tests with their names and failure reasons
- Platform-specific issues: WASM, Linux, macOS, Windows-specific failures
5. Generate fix plan
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 114 lines · 57 tokens per session scan A eacf6cc68063
diagnose-ci-failures is a skill published in the GitHub repository warpdotdev/common-skills (636 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 970 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.