メニュー
Diagnoses and fixes failing GitHub Actions checks with gh. Use when CI fails on a pull request and needs logs, focused fixes, and validation.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/TuYv/ccpm --skill fix-ciコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
Use when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix — message-matched to the destination landing page. Not for scoring an ad account — use ad-account-auditor; not for the post-click page — use landing-optimizer; not for organic articles — use content-writer. 广告创意/广告文案/RSA标题
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
SOC 職業分類に基づく
SKILL.md を表示中
| name | fix-ci |
| description | Diagnoses and fixes failing GitHub Actions checks with gh. Use when CI fails on a pull request and needs logs, focused fixes, and validation. |
Read the check state with gh pr checks, then pull the failing job logs with
gh run view <run-id> --log-failed. Logs fetched through gh are reproducible;
browser-only inspection is not. Pending checks can usually wait unless the failure is
already clear.
Reproduce locally. CI runs almost everything through Nix, so the failing step maps onto a
just recipe:
| CI job / step | Local |
|---|---|
preflight, or Run nix flake check | just check |
Run Rust tests (nix build .#ccusage-tests) | just rust::test |
JS test | just test-node |
Babashka performance harness test | apps/ccusage/scripts/compare-pr-performance_test.clj |
Start with the narrowest command that reproduces the failure — a single cargo test
filter — before the recipe above.
Fix the smallest cause that explains the failed check, using the skill for the area being
changed: testing, development, docs, or the nearest package AGENTS.md. When the
failure was generated output or formatting, commit the regenerated result the check
requires rather than hand-editing it.
Commit with the commit skill; a manifest change and its lockfile update belong in the
same commit, and unrelated cleanups belong in separate ones. Let the git hooks run.
Push, then use create-pr to comment or request another review pass when appropriate.