agentleFS
takayoshitoyoda05takayoshitoyoda05/claude-ml-template/.claude/skills/fix-ci/SKILL.md

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

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.
  • MicrosoftSkill

    act-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

  • MicrosoftSkill

    generate-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

  • jaydubya818Skill

    get-pr-comments

    Use when pull-request feedback needs to be fetched and summarized for action.

    Also in 3 projects that use this

  • SentrySkill

    create-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

  • SentrySkill

    commit

    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

The file

Files
SKILL.md

CI失敗の修正

進め方

  1. 失敗したCIのログを確認する。GitHub Actions の場合: gh run list --limit 5 で直近の実行を確認し、 gh run view <run-id> --log-failed で失敗ログを取得する。 gh コマンドが使えない場合はユーザーにログの貼り付けを依頼する。
  2. 失敗の原因を分類する。
    原因対処
    テスト失敗失敗しているテストを特定し、コードかテストのどちらが間違っているか判断する
    lint/format エラーruff check / ruff format を実行し、差分をコミットする
    依存関係エラーuv lock の実行忘れ、またはバージョン不整合を確認する
    環境差異ローカルとCI環境の違い(Pythonバージョン、OS)を確認する
  3. 修正を実装する。修正は最小限に留める(CIを通すための変更だけ)。
  4. ローカルで再現テストを実行してから push する。

注意

  • CI失敗の修正ついでに、関係ない改善をしない(最小diff規律)。
  • 原因が分からない場合は diagnosing-bugs スキルに切り替える。

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.