fix-ci
Skill8 starsChanged 2 months agoMITView on GitHub
Find failing PR checks, inspect logs or external check links, and apply focused fixes
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 30 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Prefer minimal, low-risk changes before broader refactors.
- Very specific: line 23
Keep gh pr checks as the source of truth for overall PR CI state.
“Common” is measured: kept by at least 6 in 10 of the 30 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
Trigger
Branch or PR CI is failing and needs a fast, iterative path to green checks.
Workflow
- Resolve the active PR and inspect
gh pr checks --json name,bucket,state,workflow,link. - Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.
- Apply the smallest safe fix.
- Push, re-check the PR check set, and repeat until green.
Guardrails
- Fix one actionable failure at a time.
- Prefer minimal, low-risk changes before broader refactors.
- Keep
gh pr checksas the source of truth for overall PR CI state.
Output
- Primary failing job and root error
- Fixes applied in iteration order
- Current CI status and next action
Other versions35 projects use a version of this.
Word for word · 3
- cogine-ai/cogine-dev-skillset★ 4100% same
- ElyzeSolutions/skills★ 1100% same
- ArchitektApx/cursor-skills-for-claude★ 0100% same
Edited · 4
- LedgerHQ/ledger-live★ 62259% same
- Scino/fstack★ 1894% same
- dhanji4U/skills★ 280% same
- jaydubya818/MissionControl★ 272% same
Wrote their own version · 28
- microsoft/vscode★ 194ksame name
- ryoppippi/ccusage★ 19ksame name
- ccusage/ccusage★ 19ksame name
- questdb/questdb★ 17ksame name
- fleetdm/fleet★ 7.1ksame name
- open-telemetry/opentelemetry-java-instrumentation★ 2.7ksame name
- MCPJam/inspector★ 2.3ksame name
- gronxb/hot-updater★ 1.8ksame name
- llama-farm/llamafarm★ 837same name
- dlupiak/claude-session-dashboard★ 66same name
18 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.
Used alongsideProjects with it also use create-pr, typescript and 4 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.
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
MicrosoftSkilltypescript
TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.
Also in 3 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 4 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
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 4 projects that use this
- GoogleSkill
code-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 4 projects that use this
In this repository20 other files it gives its agents.
- autonomous-maintainerSkill
- commitSkill
- competitive-ads-extractorSkill
- compress-skillsSkill
- extract-design-systemSkill
- flesch-kincaid-proofreaderSkill
- frontendSkill
- get-pr-commentsSkill
- gogSkill
- grillingSkill
- grill-meSkill
- hairline-createSkill
- image-generationSkill
- posthogSkill
- shipSkill
- signoz-investigating-alertsSkill
- teachSkill
- thermo-nuclear-code-quality-reviewSkill
- update-agents-mdSkill
- visualizeSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.