[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BV53B6F0XASJ6DZ1B1FVD":3,"skill-same:01M73BV53B6F0XASJ6DZ1B1FVD":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M73BV53B6F0XASJ6DZ1B1FVD","ci-triage",null,"Triages CI \u002F audit \u002F 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\u002Fvalidator gate blocks a sync; a scaffold or upgrade command errors; a weekly-health-check ci-failure issue needs triage.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fci-triage\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: ci-triage\nstatus: active\nscope: common\ndescription: >\n  Triages CI \u002F audit \u002F scaffold failures: deterministic reproduction,\n  minimal repro, provenance tracing, root-cause fix, and re-verification.\n  Lightweight alternative to a full project review when a single failure has\n  a single cause.\n  Use when: a CI check fails on a PR; an audit\u002Fvalidator gate blocks a sync;\n  a scaffold or upgrade command errors; a weekly-health-check ci-failure\n  issue needs triage.\nowner: pm\nversion: 0.2.0\nlast_reviewed: 2026-10-04\nprerequisites: []\nmetadata:\n  type: process\n  triggers:\n    - ci failure\n    - triage failure\n    - audit gate failed\n    - scaffold failed\n    - fix the pipeline\n  related_skills:\n    - project-review\n    - sync\n---\n\n# ci-triage\n\nLightweight loop for CI \u002F audit \u002F scaffold failures: reproduce → minimize → trace → fix →\nverify. Escalate to `project-review` (scoped mode) only when the failure spans multiple\nunrelated domains.\n\n## When to Use (and when NOT to)\n\n**Use**: one failing check, one command, one gate — including `weekly-health-check`\nci-failure issues and dev-sync gate blocks.\n**Do NOT use**: broad quality sweeps, proactive reviews, or when ≥3 unrelated domains fail\nat once (that is a `project-review` job — switch, `scoped` mode first).\n\n## Step 1 — Reproduce deterministically\n\nRe-run the exact failing command locally and capture the failing check ID verbatim:\n\n```bash\nbun scripts\u002Faudit.ts                       # or the specific validator that failed\nbun scripts\u002Fvalidate-templates.ts\nbun scripts\u002Fnew-project.ts \u003Cscratch-name> --variant \u003Cv>   # scaffold repro — scratch dir only\n```\n\nRules:\n- Scaffold reproductions go in a scratch directory **outside** `Projects\u002F`; never reproduce\n  by mutating a live project.\n- If the failure does NOT reproduce locally, suspect environment\u002Fordering (CI matrix OS,\n  node version, test ordering) — do not \"fix\" code that isn't broken.\n\n## Step 2 — Minimize\n\nStrip to the smallest input that still fails: one variant (`--domain` \u002F single file), one\nflag, one key. The goal is a one-command repro you can paste into a ticket.\n\n## Step 3 — Trace provenance\n\nFind the introducing commit and its intent:\n\n```bash\ngit log -S \"\u003Cliteral string from the failure>\" -- \u003Cfile>\ngit log --oneline -- \u003Cfile>\n```\n\nRead the introducing PR before changing anything — the mismatch may be the *other* side of\nan intentional change (proven: 2026-09-07 — a root-vs-L1 SCRIPTS.md layer-tag split traced\nto a single commit).\n\n## Step 4 — Fix at the root\n\nFix the introducing file, not the symptom site. Prefer validator\u002Fscaffold correctness over\nallowlists and `|| true`. Route implementation through the normal PM Gateway (specialists\nexecute). Never `--no-verify`, never gate bypasses.\n\n## Step 5 — Verify + harden\n\n1. Re-run the failing validator **and** the surrounding battery (at minimum:\n   `bun scripts\u002Faudit.ts` + `bun scripts\u002Fvalidate-templates.ts` + `bun scripts\u002Fverify-scripts.ts --verify`).\n2. **Ratchet rule**: if this failure class could recur unnoticed, create a\n   validator-hardening ticket:\n   `bun scripts\u002Fticket.ts create --manual \"validator-hardening: \u003Cone-sentence check>\" --priority normal`\n3. Clean up scratch artifacts (`rm -rf` the scratch project; `git status` clean).\n4. Land the fix via the standard `\u002Fsync` pipeline.\n\n## Step 6 — Merge with CI watch (merge-time healing)\n\nThe merge itself is part of the loop: a PR is not done when it opens, it is done when\nit is merged with green checks. Proven procedure (2026-10-04 wave, PRs #1376-#1382):\n\n1. **Watch, do not walk away**: `gh pr checks \u003Cpr> --watch`. Merge only on all-green.\n2. **On red, read the failed job's own log** (`gh run view \u003Crun> --log-failed | tail`),\n   then classify:\n   - **Flake \u002F slow-runner timeout** (test timed out at Ns on one OS only, same test\n     green locally and on other OSes) → give the test an explicit timeout with an\n     evidence comment (`}, 15_000);` + \"why\" comment naming the run), push, re-watch.\n   - **Real defect** → go back to Step 1 (reproduce) on the PR branch.\n   - **Registry\u002Fversion parity failures** (SCRIPTS.md, VERSION_MANIFEST drift) → run\n     the generator, land via `\u002Fsync` on the PR branch.\n3. **Sequential merges**: every `\u002Fsync` appends to shared session files\n   (`memory\u002FYYYY-MM-DD.md`), so merging one PR marks the next one conflicting.\n   Merge one PR at a time; before each next merge, update its branch from the new\n   main (`git merge origin\u002Fmain`, regenerate the version manifest if the pre-push\n   gate says so, land the branch update via `\u002Fsync`), then merge.\n4. **GitHub-side stale states**: a CONFLICTING\u002FDIRTY verdict that local\n   `git merge-tree --write-tree` contradicts is usually a stale mergeability cache —\n   update the branch (which re-computes it) instead of hand-resolving phantom conflicts.\n5. Close the PR's governance tickets (`move \u003Cid> done --result \"Delivered via PR #N…\"`)\n   and land the closure through `\u002Fsync`.\n\n## Escalation\n\n- ≥3 unrelated domains failing → `project-review` with `scoped` mode.\n- Failure only in CI (not locally) → compare OS\u002Fnode matrices first; check\n  `.github\u002Fworkflows\u002Ftest.yml` step environment before touching code.\n- Security-flavored failure (gitleaks, `bun audit`) → involve `security-expert` per §9.6.\n\n## Related Skills\n\n- **project-review**: broad multi-domain review — ci-triage is the single-failure counterpart\n- **sync**: landing pipeline for the fix\n","# ci-triage\n\nLightweight loop for CI \u002F audit \u002F scaffold failures: reproduce → minimize → trace → fix →\nverify. Escalate to `project-review` (scoped mode) only when the failure spans multiple\nunrelated domains.\n\n## When to Use (and when NOT to)\n\n**Use**: one failing check, one command, one gate — including `weekly-health-check`\nci-failure issues and dev-sync gate blocks.\n**Do NOT use**: broad quality sweeps, proactive reviews, or when ≥3 unrelated domains fail\nat once (that is a `project-review` job — switch, `scoped` mode first).\n\n## Step 1 — Reproduce deterministically\n\nRe-run the exact failing command locally and capture the failing check ID verbatim:\n\n```bash\nbun scripts\u002Faudit.ts                       # or the specific validator that failed\nbun scripts\u002Fvalidate-templates.ts\nbun scripts\u002Fnew-project.ts \u003Cscratch-name> --variant \u003Cv>   # scaffold repro — scratch dir only\n```\n\nRules:\n- Scaffold reproductions go in a scratch directory **outside** `Projects\u002F`; never reproduce\n  by mutating a live project.\n- If the failure does NOT reproduce locally, suspect environment\u002Fordering (CI matrix OS,\n  node version, test ordering) — do not \"fix\" code that isn't broken.\n\n## Step 2 — Minimize\n\nStrip to the smallest input that still fails: one variant (`--domain` \u002F single file), one\nflag, one key. The goal is a one-command repro you can paste into a ticket.\n\n## Step 3 — Trace provenance\n\nFind the introducing commit and its intent:\n\n```bash\ngit log -S \"\u003Cliteral string from the failure>\" -- \u003Cfile>\ngit log --oneline -- \u003Cfile>\n```\n\nRead the introducing PR before changing anything — the mismatch may be the *other* side of\nan intentional change (proven: 2026-09-07 — a root-vs-L1 SCRIPTS.md layer-tag split traced\nto a single commit).\n\n## Step 4 — Fix at the root\n\nFix the introducing file, not the symptom site. Prefer validator\u002Fscaffold correctness over\nallowlists and `|| true`. Route implementation through the normal PM Gateway (specialists\nexecute). Never `--no-verify`, never gate bypasses.\n\n## Step 5 — Verify + harden\n\n1. Re-run the failing validator **and** the surrounding battery (at minimum:\n   `bun scripts\u002Faudit.ts` + `bun scripts\u002Fvalidate-templates.ts` + `bun scripts\u002Fverify-scripts.ts --verify`).\n2. **Ratchet rule**: if this failure class could recur unnoticed, create a\n   validator-hardening ticket:\n   `bun scripts\u002Fticket.ts create --manual \"validator-hardening: \u003Cone-sentence check>\" --priority normal`\n3. Clean up scratch artifacts (`rm -rf` the scratch project; `git status` clean).\n4. Land the fix via the standard `\u002Fsync` pipeline.\n\n## Step 6 — Merge with CI watch (merge-time healing)\n\nThe merge itself is part of the loop: a PR is not done when it opens, it is done when\nit is merged with green checks. Proven procedure (2026-10-04 wave, PRs #1376-#1382):\n\n1. **Watch, do not walk away**: `gh pr checks \u003Cpr> --watch`. Merge only on all-green.\n2. **On red, read the failed job's own log** (`gh run view \u003Crun> --log-failed | tail`),\n   then classify:\n   - **Flake \u002F slow-runner timeout** (test timed out at Ns on one OS only, same test\n     green locally and on other OSes) → give the test an explicit timeout with an\n     evidence comment (`}, 15_000);` + \"why\" comment naming the run), push, re-watch.\n   - **Real defect** → go back to Step 1 (reproduce) on the PR branch.\n   - **Registry\u002Fversion parity failures** (SCRIPTS.md, VERSION_MANIFEST drift) → run\n     the generator, land via `\u002Fsync` on the PR branch.\n3. **Sequential merges**: every `\u002Fsync` appends to shared session files\n   (`memory\u002FYYYY-MM-DD.md`), so merging one PR marks the next one conflicting.\n   Merge one PR at a time; before each next merge, update its branch from the new\n   main (`git merge origin\u002Fmain`, regenerate the version manifest if the pre-push\n   gate says so, land the branch update via `\u002Fsync`), then merge.\n4. **GitHub-side stale states**: a CONFLICTING\u002FDIRTY verdict that local\n   `git merge-tree --write-tree` contradicts is usually a stale mergeability cache —\n   update the branch (which re-computes it) instead of hand-resolving phantom conflicts.\n5. Close the PR's governance tickets (`move \u003Cid> done --result \"Delivered via PR #N…\"`)\n   and land the closure through `\u002Fsync`.\n\n## Escalation\n\n- ≥3 unrelated domains failing → `project-review` with `scoped` mode.\n- Failure only in CI (not locally) → compare OS\u002Fnode matrices first; check\n  `.github\u002Fworkflows\u002Ftest.yml` step environment before touching code.\n- Security-flavored failure (gitleaks, `bun audit`) → involve `security-expert` per §9.6.\n\n## Related Skills\n\n- **project-review**: broad multi-domain review — ci-triage is the single-failure counterpart\n- **sync**: landing pipeline for the fix\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":38,"last_reviewed":39,"prerequisites":40},"pm","common","active","0.2.0",{"type":28,"triggers":29,"related_skills":35},"process",[30,31,32,33,34],"ci failure","triage failure","audit gate failed","scaffold failed","fix the pipeline",[36,37],"project-review","sync","Triages CI \u002F audit \u002F 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\u002Fvalidator gate blocks a sync; a scaffold or upgrade command errors; a weekly-health-check ci-failure issue needs triage.\n",1791072000000,[],"main","1162ccc568cf90c01b3886d6143cbfd851a37883",".codex\u002Fskills\u002Fci-triage",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill ci-triage",{"tool":55,"command":56},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill ci-triage",{"tool":58,"command":59},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill ci-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fci-triage\u002FSKILL.md",true,[],[64,72,77,82,87,92],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi 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\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":71},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":78,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":71},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":83,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":71},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":88,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":71},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":93,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":71},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]