fix-ci
Skill1 starsChanged 2 months agoMITView on GitHub
CIが失敗したとき、「CIを直して」「テストが落ちている」と言われたときに必ず使う。
46 other projects use a version of this.
Adopted by
Most recently taken up by
- pauljasperdev/skillstheir own version, first seen Nov 16, 2026
- bhagyamudgal/skillstheir own version, first seen Nov 16, 2026
- ClickHouse/ClickHousetheir own version, first seen Nov 15, 2026
- DocSpring/docspring-agent-playbooktheir own version, first seen Nov 15, 2026
- Trixx4191/asrartheir own version, first seen Nov 15, 2026
- digitaltracer/agent-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use act-on-feedback, generate-run-commands and 10 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.
MicrosoftSkillact-on-feedback
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
Also in 3 projects that use this
MicrosoftSkillgenerate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
Also in 3 projects that use this
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 11 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 13 projects that use this
- +7 more from microsoft
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 46
- microsoft/vscode★ 195ksame name
- ClickHouse/ClickHouse★ 51ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 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
36 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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adrSkill
- architecture-checkSkill
- brainstormSkill
- branch-namingSkill
- codex-delegateSkill
- config-explainSkill
- config-setSkill
- cross-reviewSkill
- design-interviewSkill
- diagnosing-bugsSkill
- handoffSkill
- leakage-checkSkill
- literature-reviewSkill
- mlflow-logSkill
- multi-seedSkill
- mutation-testSkill
- paper-writingSkill
- pre-mortemSkill
- property-testSkill
- python-standardsSkill
- refactor-scoutSkill
- regression-suiteSkill
- retrospectiveSkill
- security-reviewSkill
- spec-checklistSkill
- tddSkill
The file
Files
CI失敗の修正
進め方
- 失敗したCIのログを確認する。GitHub Actions の場合:
gh run list --limit 5で直近の実行を確認し、gh run view <run-id> --log-failedで失敗ログを取得する。 gh コマンドが使えない場合はユーザーにログの貼り付けを依頼する。 - 失敗の原因を分類する。
原因 対処 テスト失敗 失敗しているテストを特定し、コードかテストのどちらが間違っているか判断する lint/format エラー ruff check/ruff formatを実行し、差分をコミットする依存関係エラー uv lockの実行忘れ、またはバージョン不整合を確認する環境差異 ローカルとCI環境の違い(Pythonバージョン、OS)を確認する - 修正を実装する。修正は最小限に留める(CIを通すための変更だけ)。
- ローカルで再現テストを実行してから push する。
注意
- CI失敗の修正ついでに、関係ない改善をしない(最小diff規律)。
- 原因が分からない場合は diagnosing-bugs スキルに切り替える。
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.

