ci-triage
Triages CI / audit / scaffold failures: deterministic reproduction, minimal repro, provenance tracing, root-cause fix, and re-verification. Lightweight alternative to a full project review when a single failure has a single cause. Use when: a CI check fails on a PR; an audit/validator gate blocks a sync; a scaffold or upgrade command errors; a weekly-health-check ci-failure issue needs triage.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- ci-triage
- owner
- pm
- scope
- common
- status
- active
- version
- 0.2.0
- metadata
- { "type": "process", "triggers": [ "ci failure", "triage failure", "audit gate failed", "scaffold failed", "fix the pipeline" ], "related_skills": [ "project-review", "sync" ] }
- description
- Triages CI / audit / scaffold failures: deterministic reproduction, minimal repro, provenance tracing, root-cause fix, and re-verification. Lightweight alternative to a full project review when a single failure has a single cause. Use when: a CI check fails on a PR; an audit/validator gate blocks a sync; a scaffold or upgrade command errors; a weekly-health-check ci-failure issue needs triage.
- last_reviewed
- 1791072000000
- prerequisites
- []
03 SKILL.md 正文
ci-triage
Lightweight loop for CI / audit / scaffold failures: reproduce → minimize → trace → fix →
verify. Escalate to project-review (scoped mode) only when the failure spans multiple
unrelated domains.
When to Use (and when NOT to)
Use: one failing check, one command, one gate — including weekly-health-check
ci-failure issues and dev-sync gate blocks.
Do NOT use: broad quality sweeps, proactive reviews, or when ≥3 unrelated domains fail
at once (that is a project-review job — switch, scoped mode first).
Step 1 — Reproduce deterministically
Re-run the exact failing command locally and capture the failing check ID verbatim:
bun scripts/audit.ts # or the specific validator that failed
bun scripts/validate-templates.ts
bun scripts/new-project.ts <scratch-name> --variant <v> # scaffold repro — scratch dir only
Rules:
- Scaffold reproductions go in a scratch directory outside
Projects/; never reproduce by mutating a live project. - If the failure does NOT reproduce locally, suspect environment/ordering (CI matrix OS, node version, test ordering) — do not "fix" code that isn't broken.
Step 2 — Minimize
Strip to the smallest input that still fails: one variant (--domain / single file), one
flag, one key. The goal is a one-command repro you can paste into a ticket.
Step 3 — Trace provenance
Find the introducing commit and its intent:
git log -S "<literal string from the failure>" -- <file>
git log --oneline -- <file>
Read the introducing PR before changing anything — the mismatch may be the other side of an intentional change (proven: 2026-09-07 — a root-vs-L1 SCRIPTS.md layer-tag split traced to a single commit).
Step 4 — Fix at the root
Fix the introducing file, not the symptom site. Prefer validator/scaffold correctness over
allowlists and || true. Route implementation through the normal PM Gateway (specialists
execute). Never --no-verify, never gate bypasses.
Step 5 — Verify + harden
- Re-run the failing validator and the surrounding battery (at minimum:
bun scripts/audit.ts+bun scripts/validate-templates.ts+bun scripts/verify-scripts.ts --verify). - Ratchet rule: if this failure class could recur unnoticed, create a
validator-hardening ticket:
bun scripts/ticket.ts create --manual "validator-hardening: <one-sentence check>" --priority normal - Clean up scratch artifacts (
rm -rfthe scratch project;git statusclean). - Land the fix via the standard
/syncpipeline.
Step 6 — Merge with CI watch (merge-time healing)
The merge itself is part of the loop: a PR is not done when it opens, it is done when it is merged with green checks. Proven procedure (2026-10-04 wave, PRs #1376-#1382):
- Watch, do not walk away:
gh pr checks <pr> --watch. Merge only on all-green. - On red, read the failed job's own log (
gh run view <run> --log-failed | tail), then classify:- Flake / slow-runner timeout (test timed out at Ns on one OS only, same test
green locally and on other OSes) → give the test an explicit timeout with an
evidence comment (
}, 15_000);+ "why" comment naming the run), push, re-watch. - Real defect → go back to Step 1 (reproduce) on the PR branch.
- Registry/version parity failures (SCRIPTS.md, VERSION_MANIFEST drift) → run
the generator, land via
/syncon the PR branch.
- Flake / slow-runner timeout (test timed out at Ns on one OS only, same test
green locally and on other OSes) → give the test an explicit timeout with an
evidence comment (
- Sequential merges: every
/syncappends to shared session files (memory/YYYY-MM-DD.md), so merging one PR marks the next one conflicting. Merge one PR at a time; before each next merge, update its branch from the new main (git merge origin/main, regenerate the version manifest if the pre-push gate says so, land the branch update via/sync), then merge. - GitHub-side stale states: a CONFLICTING/DIRTY verdict that local
git merge-tree --write-treecontradicts is usually a stale mergeability cache — update the branch (which re-computes it) instead of hand-resolving phantom conflicts. - Close the PR's governance tickets (
move <id> done --result "Delivered via PR #N…") and land the closure through/sync.
Escalation
- ≥3 unrelated domains failing →
project-reviewwithscopedmode. - Failure only in CI (not locally) → compare OS/node matrices first; check
.github/workflows/test.ymlstep environment before touching code. - Security-flavored failure (gitleaks,
bun audit) → involvesecurity-expertper §9.6.
Related Skills
- project-review: broad multi-domain review — ci-triage is the single-failure counterpart
- sync: landing pipeline for the fix
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.