ci-fix
Skill9 starsChanged 7 months agoApache-2.0View on GitHub
Auto-fix CI failures (lint, format, type errors). Diagnoses, fixes, commits and pushes.
- Commits and pushes
8 other projects use a version of this.
Adopted by
Most recently taken up by
- oasm-platform/open-asmtheir own version, first seen Oct 29, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- Cosmian/kmstheir own version, first seen Oct 8, 2026
- FastLED/FastLEDtheir own version, first seen Oct 8, 2026
- dotnet/mauitheir own version, first seen Oct 8, 2026
- Twigpine/openclaude-skillstheir own version, first seen May 14, 2026
Used with
Projects with it also use pr-review.
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.
MicrosoftSkillpr-review
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- dotnet/maui★ 23ksame name
- FastLED/FastLED★ 7.5ksame name
- warpdotdev/oz-skills★ 825same name
- Cosmian/kms★ 372same name
- oasm-platform/open-asm★ 272same name
- jMerta/codex-skills★ 130same name
- Twigpine/openclaude-skills★ 19same name
- davidanthonyn/claude-skills★ 0same name
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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- control-plane-api/CLAUDE.mdCLAUDE.md
- control-plane-ui/CLAUDE.mdCLAUDE.md
- e2e/CLAUDE.mdCLAUDE.md
- portal/CLAUDE.mdCLAUDE.md
- stoa-gateway/CLAUDE.mdCLAUDE.md
- analyticsSkill
- cartoSkill
- ci-debugSkill
- competitive-watchSkill
- councilSkill
- decomposeSkill
- extractSkill
- fill-cycleSkill
- generate-backlogSkill
- impactSkill
- memory-consolidateSkill
- monitor-cdSkill
- parallel-reviewSkill
- pr-guardianSkill
- rewriteSkill
- roadmapSkill
- spec-drivenSkill
- sync-planSkill
- verify-megaSkill
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 8 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 26
If workflow run URL or ID:
- Distinctive: line 63
If the failure is NOT auto-fixable, report what you found and stop.
- Distinctive: line 67
Run the appropriate fix command from the table above.
- Very specific: line 133
NEVER: use --force push
- Very specific: line 134
NEVER: use --no-verify on commits
- Distinctive: line 136
If the fix changes behavior (not just formatting), STOP and report
- Distinctive: line 137
If unsure whether a fix is safe, STOP and report
- Distinctive: line 138
Always verify the fix locally before pushing
“Common” is measured: kept by at least 6 in 10 of the 8 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
CI Fix — Auto-remediate CI Failures
Context dynamique
- Branch courante: !
git branch --show-current - Checks PR en cours: !
gh pr checks 2>/dev/null | head -20 - Workflows recents: !
gh run list --limit 5 --json name,status,conclusion,headBranch --template '{{range .}}{{.name}} | {{.status}} | {{.conclusion}} | {{.headBranch}}{{"\n"}}{{end}}' 2>/dev/null
Instructions
Auto-fix CI failure for: $ARGUMENTS
Step 1: Identify failing checks
If PR number:
gh pr checks $ARGUMENTS
gh run list --branch $(gh pr view $ARGUMENTS --json headRefName -q .headRefName) --limit 3If workflow run URL or ID:
gh run view $ARGUMENTS --log-failedStep 2: Read error logs
# Get the failed run ID, then read logs
gh run view <run-id> --log-failed 2>&1 | head -200Step 3: Classify — auto-fixable or manual?
Auto-fixable (proceed to Step 4):
| Check | Error pattern | Fix command |
| Python lint (ruff) | Found N errors | cd <component> && ruff check --fix . |
| Python format (black) | would reformat | cd <component> && black . |
| Python import order | I001 | cd <component> && ruff check --fix --select I . |
| TS/JS lint (eslint) | N problems (N errors, N warnings) | cd <component> && npm run lint -- --fix |
| TS/JS format (prettier) | Code style issues | cd <component> && npx prettier --write . |
| Rust format | Diff in | cd stoa-gateway && cargo fmt |
| Rust clippy (simple) | warning: with help: ... suggestion | cd stoa-gateway && cargo clippy --fix --allow-dirty |
NOT auto-fixable (report and STOP):
| Category | Examples |
| Logic errors | Test assertions failing, wrong behavior |
| Test failures | vitest/pytest/cargo test failures |
| Security issues | Gitleaks, Bandit findings, SAST violations |
| Type errors (complex) | Missing interfaces, wrong generics |
| Build errors | Missing dependencies, Docker build failures |
| Infrastructure | K8s deploy, ArgoCD, Helm issues |
If the failure is NOT auto-fixable, report what you found and stop. Do NOT attempt manual fixes.
Step 4: Apply fix
Run the appropriate fix command from the table above. Then verify locally:
Python:
cd <component> && ruff check . && black --check .TypeScript:
cd <component> && npm run lint && npm run format:checkRust:
cd stoa-gateway && cargo fmt --check && RUSTFLAGS=-Dwarnings cargo clippy --all-targets --all-features -- -D warningsStep 5: Commit and push
GUARDRAILS (mandatory checks before any git operation):
# Verify we are NOT on main
BRANCH=$(git branch --show-current)
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
echo "ABORT: Cannot push CI fixes to main. Checkout the feature branch first."
exit 1
fiThen commit and push:
git add <only-fixed-files>
git commit -m "fix(ci): auto-fix <check-name> lint/format issues"
git pushStep 6: Report
## CI Fix: [check-name] on [branch]
### Fixed
- **Check**: [failing check name]
- **Error**: [error summary]
- **Fix**: [command run]
- **Files**: [list of modified files]
### Verification
- Local check: PASS/FAIL
- Pushed to: [branch]
### Not Fixed (if any)
- [check]: [reason — requires manual intervention]Append metrics entry:
Append to ~/.claude/projects/.../memory/metrics.log:
YYYY-MM-DDTHH:MM | CI-FIX | task=<current-task> check=<check-name> auto_fixed=true|falseRules
- NEVER fix logic errors, test failures, or security issues — only format/lint/type
- NEVER push to main — always verify branch name first
- NEVER use
--forcepush - NEVER use
--no-verifyon commits - NEVER modify test expectations to make them pass
- If the fix changes behavior (not just formatting), STOP and report
- If unsure whether a fix is safe, STOP and report
- Always verify the fix locally before pushing
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.

