feat(skill): ci-expedition — diagnose CI failures by signature - #1731
Conversation
Codifies the 2026-06-05/06 GHCR cascade into a decode-by-signature triage skill: startup_failure (YAML break / Actions allowlist) vs Trivy disk-no-space vs cancel vs real-CVE — each with the matching fix + verification cadence + the guard-safe runner-hygiene recipe. Turns 'CI is red again' into 30-second triage. Source: memory reference_ghcr_ci_failure_playbook. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR introduces a new ci-expedition playbook document that provides a complete diagnostic framework for PMOVES CI/GHCR red failures. The document teaches signature-based failure classification, Trivy CVE extraction from logs, dependency remediation procedures, verification workflows, safe runner hygiene commands, and explicit anti-patterns to avoid. ChangesCI Failure Diagnosis Playbook
🎯 1 (Trivial) | ⏱️ ~3 minutes
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d2d9111f21
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…-Go check Address Codex P2 review threads on PR #1731: - gh api substitutes {owner}/{repo}/{branch}, not {o}/{r} - embedded-Go verifier now takes the binary path via sys.argv (BIN was undefined in Python) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
What
Adds a project skill
.claude/skills/ci-expedition/SKILL.mdthat turns 'CI is red again' into a 30-second decode-by-signature triage.Why
The 2026-06-05/06 GHCR cascade (#1717/#1718/#1719/#1721/#1726/#1728/#1729) was five distinct failure modes wearing one red badge: uncompilable-workflow startup_failure, Actions-allowlist startup_failure, Trivy disk-no-space, concurrency/runner cancel, and real dep CVEs. Each was re-diagnosed from scratch. This skill captures the signatures + matching fixes so the next dive is a prepped expedition, not an excavation.
Contents
Pairs with memories reference_ghcr_ci_failure_playbook, feedback_no_docker_volume_prune, feedback_pr_trim_classifier_not_authoritative. Skill-only — no code or workflow changes.
Generated with Claude Code
Summary by CodeRabbit