fix-ci
Skill1 starsChanged 16 days agoMITView on GitHub
Make a failing pipeline check green by reproducing it locally and fixing the cause. Use when CI failed, a required check is red, or the user pastes a failing job log. Do not skip, delete, or weaken the failing test to get green.
39 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Yeachan-Heo/oh-my-claude-sisyphustheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- salvo8519/fairmarktheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- ArchitektApx/cursor-skills-for-claudetheir own version, first seen Nov 1, 2026
- therapys/dotagentstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use get-pr-comments, create-pr and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jaydubya818Skillget-pr-comments
Use when pull-request feedback needs to be fetched and summarized for action.
Also in 3 projects that use this
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 10 projects that use this
MicrosoftSkillmerge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.
Also in 3 projects that use this
- SentrySkill
security-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 4 projects that use this
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions39 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- rpraharaj/ai-sdlc★ 037% same
Wrote their own version · 38
- microsoft/vscode★ 195ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- questdb/questdb★ 18ksame name
- fleetdm/fleet★ 7.2ksame name
- open-telemetry/opentelemetry-java-instrumentation★ 2.7ksame name
- MCPJam/inspector★ 2.3ksame name
- gronxb/hot-updater★ 1.8ksame name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- open-prSkill
- performanceSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- resolve-conflictsSkill
- revert-changeSkill
- review-changeSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- start-projectSkill
- upgrade-depsSkill
- verify-uiSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-prdSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 37 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read AGENTS.md if present.
- Very specific: line 24
If gh or glab works and the user pointed at a PR/MR or run, fetch that log.
- Distinctive: line 26
If you cannot name the command, stop and say what you need.
- Distinctive: line 30
Run the same command, or the closest AGENTS.md Test / Lint / Typecheck / Build that implements that check.
- Very specific: line 38
Follow debug: carry forward the failing command, baseline, and evidence already collected here instead of restarting diagnosis.
- Distinctive: line 55
Run neighboring checks you might have broken (Test / Lint if cheap).
- Distinctive: line 56
If the user wants it on the PR, commit only if they asked, then push only if they asked.
- Distinctive: line 66
If the suite is red for a different reason than this check, list it.
“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fix CI
Green the same check that failed. This is debug aimed at a pipeline job, not a new feature.
Read AGENTS.md if present.
Step 1 — Identify the check
From the user, the PR/MR status, or a job log, record:
- Check / job name
- Command the job ran (from the workflow file or the log)
- Error text and first failing file
If gh or glab works and the user pointed at a PR/MR or run, fetch that log. If not, use the pasted log or open the workflow file under .github/workflows, .gitlab-ci.yml, or whatever this repo uses.
If you cannot name the command, stop and say what you need.
Step 2 — Reproduce locally
Run the same command, or the closest AGENTS.md Test / Lint / Typecheck / Build that implements that check.
- Same failure → you have a baseline. Continue.
- Cannot run (missing service, runner OS) → say what is missing; do not guess a fix.
- Passes locally but failed in CI → compare versions, env vars, secrets, and file set. Do not "fix" passing local tests.
Step 3 — Fix the cause
Follow debug: carry forward the failing command, baseline, and evidence already collected here instead of restarting diagnosis. Test one hypothesis at a time, then make the smallest cause-level change.
Forbidden:
- Deleting or skipping the failing test
- Weakening an assertion to hide the bug
- Disabling the workflow job or
continue-on-error --no-verifyas the solution- Pinning a broken dependency with no explanation
Allowed: fix product code, fix the test if the test is wrong, update a fixture, match a version the repo already intended.
Load engineering-bar (paths in that skill). If the failure is a flake (order, time, network), make the test deterministic — do not retry-loop the job.
Step 4 — Prove
- Re-run the same local command. It must pass.
- Run neighboring checks you might have broken (Test / Lint if cheap).
- If the user wants it on the PR, commit only if they asked, then push only if they asked. Otherwise report that CI still has to run remotely.
Done
- Check name + command
- Root cause
- Fix (files)
- Local re-run output
- What you did not change (jobs left enabled, assertions still strict)
If the suite is red for a different reason than this check, list it; do not silently expand scope.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.