Individual skill
comet-github-ci-triage
使用 PR 当前准确 head、失败 job 日志、本地复现边界和可合并状态,诊断 Comet PR 的 GitHub Actions 与覆盖率检查。PR 出现 CI 报错、Codecov 问题、过期检查或无法解释的红色 job 时使用。
assets/skills-maintainer/comet-github-ci-triage/SKILL.md
Source commit 1fb0f070582714f8dd36cd01b7681a8aa0310942
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,280
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- harness-engineering Repository topic
- sdd Repository topic
- skills Repository topic
- spec Repository topic
- eval Repository topic
- skill-creator Repository topic
- phase-guarded Repository topic
- loop-engineering Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,001 bytesagents/openai.yamlasset · 235 bytes
Read excerpt
# Comet GitHub CI 分诊
先读取 `../comet-github/references/maintainer-contract.md`。默认只做诊断;只有用户要求时才实施修复。
## 检查准确的远端状态
1. 解析 PR,记录当前 head SHA 和目标分支。
2. 运行 `gh pr checks <pr> --json name,state,bucket,link,workflow,startedAt,completedAt`。
3. 对失败 job 使用 `gh run view <run-id> --log-failed` 或最小范围的 job 日志检查真实失败边界。不要在没有日志证据时相信聚合助手摘要。
4. 检查可合并状态,并确认显示的检查属于当前 head。过期 run 不能证明当前代码有问题。
5. Codecov 页面信息不完整时,通过可用 API 检查受影响文件和 patch coverage 元数据,并报告准确 head 和覆盖率范围。
## 分类失败原因