agentleFS
shinobiashishinobiashi/claude-skills/skills/ci-triage/SKILL.md

ci-triage

Skill0 starsChanged 2 months agoNo licenceView on GitHub

GitHub Actions の CI 失敗を「コード起因」か「インフラ起因(課金・ランナー・ ワークフロー設定・キャッシュ)」かに切り分けるスキル。失敗ジョブの所要時間と ステップ実行有無から当たりを付け、`gh run view --log-failed` が空振りする ケース(ジョブ自体が起動していない場合)では check-runs の annotations を 読んで原因を特定する。「CIが落ちた」「CIが真っ赤」「全部failしてる」 「なぜ落ちたか調べて」「ci triage」「CI失敗の原因」といった依頼で使う。 ローカルでは通るのに CI だけ落ちる場合の環境差の確認手順も含む。 PR が触っていないファイルで落ちる(分岐元が古く main で修正済み)ケースの判定と ブランチ更新の手順も含む。 引数: PR番号 または run ID(省略時は現在のブランチの PR)。

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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.