[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CC31R6D2XWD61XPEPNQNJ":3,"skill-same:01M73CC31R6D2XWD61XPEPNQNJ":65},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M73CC31R6D2XWD61XPEPNQNJ","context-commonization-review",null,"Reviews cross-variant docs\u002F\u003Cvariant>.context.md duplication and promotes genuinely shared content into the common docs\u002Fcontext.md (ADR-0050 Part 3). Use when: after scaffolding a new variant, on a periodic cadence (every 5 new variants or quarterly, whichever first), or on-demand when asked to check for or reduce context.md duplication across variants.","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\u002Fskills\u002Fcontext-commonization-review\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: context-commonization-review\ndescription: >\n  Reviews cross-variant docs\u002F\u003Cvariant>.context.md duplication and promotes genuinely\n  shared content into the common docs\u002Fcontext.md (ADR-0050 Part 3).\n  Use when: after scaffolding a new variant, on a periodic cadence (every 5 new\n  variants or quarterly, whichever first), or on-demand when asked to check for or\n  reduce context.md duplication across variants.\nstatus: active\nscope: workspace\nl2_propagate: false\nversion: \"1.1.0\"\nowner: architect\nlast_reviewed: 2026-11-08\nrelates_to:\n  - skill: promote-variant\n    type: follows\n  - skill: meeting-facilitation\n    type: follows\nmetadata:\n  type: process\n  triggers:\n    - context commonization review\n    - variant context duplication\n    - commonization review\n    - context.md duplication review\n    - context.md commonization\n---\n\n# Skill: context-commonization-review\n\n## When to Use\n\n- Immediately after scaffolding a new variant (`create-variant` skill) — a natural checkpoint\n  to check whether the new variant's `docs\u002F\u003Cvariant>.context.md` duplicates existing patterns.\n- At minimum every 5 new variants or once per quarter since the last review, whichever comes\n  first (ADR-0050 Part 3) — variant count, not just calendar time, drives duplication risk.\n- On-demand, whenever asked to look for or reduce `docs\u002Fcontext.md` \u002F `docs\u002F\u003Cvariant>.context.md`\n  duplication.\n\nThis skill is the execution half of a two-part mechanism: `scripts\u002Faudit.ts`'s\n`checkVariantContextCommonization()` is the detection half (always runs, WARN-only).\n\n## Step-by-Step Procedure\n\n### 1. Detect candidates\n\n```bash\nbun scripts\u002Faudit.ts 2>&1 | grep \"Context commonization candidate\"\n```\n\nEach line names a section heading, the overlap percentage, and which variants are involved\n— e.g. `\"git \u002F pr workflow\" section is >50% similar (83-100% overlap) across 6\u002F10 variants: ...`.\n\n### 2. Decide, per candidate (architect judgment — not automatable)\n\nFor each flagged heading, per ADR-0050 Part 3's criteria:\n\n| Situation | Decision |\n|---|---|\n| Shared by nearly all variants, content is genuinely identical or should be | **Promote** to `docs\u002Fcontext.md` |\n| Shared by only a subset of variants (e.g. a domain cluster) | **Extract** into a shared skill or `docs\u002F_common\u002F` reference those variants opt into — do not bloat `docs\u002Fcontext.md` for variants that don't need it |\n| Similar today by coincidence, variants expected to diverge later | **Leave alone** |\n| High overlap % but with a meaningful per-variant difference (e.g. a different commit-type convention, a different threshold) | **Do not promote as-is** — either exclude the diverging variant from the promotion, or conclude the sections aren't actually the same thing despite the heading match |\n\n`scripts\u002Fpromote-context-section.ts` (step 3) always prints a line-level diff against the\ncanonical source before writing anything — read it. A high overlap percentage is a hint, not\na verdict; text that reads as \"83% similar\" can still carry a deliberate, load-bearing\ndifference (verified in practice: a `git \u002F pr workflow` promotion attempt across 6 variants\nfound `co-security` used `\u002Fsync \"security: ...\"` where the others used `\u002Fsync \"feat: ...\"`\n— textually close, semantically not interchangeable).\n\n### 3. Execute a promotion\n\n```bash\nbun scripts\u002Fpromote-context-section.ts \\\n  --heading \"\u003Cheading text, exactly as it appears in audit.ts's output>\" \\\n  --variants co-a,co-b,co-c \\\n  [--source \u003Cvariant>]         # which variant's text becomes canonical (default: first listed)\n  [--after-heading \"\u003Ctext>\"]   # where in docs\u002Fcontext.md to insert (default: before Lifecycle Management)\n  [--dry-run]                  # always run this first\n```\n\nReview the dry-run output — the per-variant content preview and any divergence warnings —\nbefore re-running without `--dry-run`. The script:\n- Inserts the canonical section into `templates\u002Fcommon\u002Fdocs\u002Fcontext.md` and bumps its version footer\n- Removes the section from each listed variant's `templates\u002F\u003Cvariant>\u002Fdocs\u002F\u003Cvariant>.context.md`\n- Does **not** decide anything and does **not** touch already-scaffolded projects (see step 4)\n\n**Fixed 2026-09-22 — nested `###` subsections are no longer dropped.** Earlier versions\nof the tool removed the promoted section with a regex that stopped at the *next* `#{2,3}`\nheading, so if the promoted `##` section had a nested `###` subsection, that subsection was\nexcluded from both the removal (left behind as an orphaned, parent-less duplicate in the\nvariant file) *and* the canonical content copied into `docs\u002Fcontext.md` (never appeared\nthere either) — real content loss if no other copy of that subsection existed elsewhere in\nthe file. Hit in practice promoting \"Scripts\" (`### Hybrid Scripting` nested underneath):\n7 variant files were left with an orphaned duplicate, and `co-consult`\u002F`co-export`\ngenuinely lost the content since neither had a second copy elsewhere. Fixed in\n`promote-context-section.ts` v1.1.0 (nesting-aware spans, `helpers\u002Fcontext-sections.ts`\nv1.6.0): a promoted `##` section now carries its `###` children into `docs\u002Fcontext.md` AND\nremoves them from every variant file; fenced `#` lines never terminate a section. The\ndry-run preview notes when a candidate section includes nested subsections.\n\n### 4. Handle already-scaffolded projects\n\nRemoving a section from `templates\u002F\u003Cvariant>\u002Fdocs\u002F\u003Cvariant>.context.md` only fixes *future*\nscaffolds (`new-project.ts`, `create-l3-scaffold.ts`) and stops `audit.ts` from re-flagging the\n*template*. Existing `Projects\u002F*\u002Fdocs\u002F\u003Cvariant>.context.md` files keep the old duplicated text\n— there is no automated cleanup path for this (the file isn't a managed-block merge target, so\n`upgrade-project.ts` can't safely delete arbitrary content from it). Either:\n- manually remove the now-redundant section from each affected existing project, or\n- accept the duplication there until an unrelated future edit touches that section.\n\nThen, for each existing project of the affected variants, pick up the *promoted* content into\n`docs\u002Fcontext.md`:\n\n```bash\nbun scripts\u002Fupgrade-project.ts \u003Cproject-path> --variant \u003Cvariant> --dry-run\n```\n\n### 5. Extraction path (subset-shared content)\n\nWhen step 2 decides a candidate should become a shared skill instead of promoting to\n`docs\u002Fcontext.md`: create `skills\u002F\u003Cname>\u002FSKILL.md` with the shared content, update the affected\nvariants' `agents\u002Fpm.md` or `AGENTS.md` to reference it, then manually remove the duplicated\nprose from each affected variant's `docs\u002F\u003Cvariant>.context.md` (`promote-context-section.ts`\nonly targets `docs\u002Fcontext.md` as the promotion destination — it's not a general dedup tool for\nskills, since skill placement\u002Fwiring per variant needs its own review).\n\n### 6. Verify and log\n\n```bash\nbun scripts\u002Faudit.ts   # the promoted heading should no longer appear as a candidate\n```\n\nLog the decision and rationale in the session's `memory\u002FYYYY-MM-DD.md` — this is the audit\ntrail ADR-0050 Part 3 relies on for \"why was this promoted\u002Fleft alone\" questions later.\n\n## See Also\n\n- ADR-0050 Part 3 (Variant Script Inheritance and Golden-Reference SSOT — Context Commonization\n  Review) — full rationale, thresholds, and open questions\n- `templates\u002Fcommon\u002Fdocs\u002Fcontext.md` § Lifecycle Management § Context Commonization Review\n- `skills\u002Fupgrade-project\u002FSKILL.md` — how promoted `docs\u002Fcontext.md` content reaches existing projects\n- `skills\u002Fcreate-variant\u002FSKILL.md` — the natural trigger point after scaffolding a new variant\n- `docs\u002Fgovernance\u002Fvariant-contract.md` § Context.md Structure Standard (`validate-templates.ts`\n  Check WS-09) — a related but distinct concern: this skill promotes\u002Fdedups *content* that's\n  duplicated across variants; WS-09 instead enforces that every variant's `docs\u002F\u003Cvariant>.context.md`\n  has the same top-level *structure* (slot presence + order), regardless of whether the content in\n  each slot is shared or variant-specific. Content standardization was explicitly considered and\n  rejected during WS-09's design — see that doc for why.\n","# Skill: context-commonization-review\n\n## When to Use\n\n- Immediately after scaffolding a new variant (`create-variant` skill) — a natural checkpoint\n  to check whether the new variant's `docs\u002F\u003Cvariant>.context.md` duplicates existing patterns.\n- At minimum every 5 new variants or once per quarter since the last review, whichever comes\n  first (ADR-0050 Part 3) — variant count, not just calendar time, drives duplication risk.\n- On-demand, whenever asked to look for or reduce `docs\u002Fcontext.md` \u002F `docs\u002F\u003Cvariant>.context.md`\n  duplication.\n\nThis skill is the execution half of a two-part mechanism: `scripts\u002Faudit.ts`'s\n`checkVariantContextCommonization()` is the detection half (always runs, WARN-only).\n\n## Step-by-Step Procedure\n\n### 1. Detect candidates\n\n```bash\nbun scripts\u002Faudit.ts 2>&1 | grep \"Context commonization candidate\"\n```\n\nEach line names a section heading, the overlap percentage, and which variants are involved\n— e.g. `\"git \u002F pr workflow\" section is >50% similar (83-100% overlap) across 6\u002F10 variants: ...`.\n\n### 2. Decide, per candidate (architect judgment — not automatable)\n\nFor each flagged heading, per ADR-0050 Part 3's criteria:\n\n| Situation | Decision |\n|---|---|\n| Shared by nearly all variants, content is genuinely identical or should be | **Promote** to `docs\u002Fcontext.md` |\n| Shared by only a subset of variants (e.g. a domain cluster) | **Extract** into a shared skill or `docs\u002F_common\u002F` reference those variants opt into — do not bloat `docs\u002Fcontext.md` for variants that don't need it |\n| Similar today by coincidence, variants expected to diverge later | **Leave alone** |\n| High overlap % but with a meaningful per-variant difference (e.g. a different commit-type convention, a different threshold) | **Do not promote as-is** — either exclude the diverging variant from the promotion, or conclude the sections aren't actually the same thing despite the heading match |\n\n`scripts\u002Fpromote-context-section.ts` (step 3) always prints a line-level diff against the\ncanonical source before writing anything — read it. A high overlap percentage is a hint, not\na verdict; text that reads as \"83% similar\" can still carry a deliberate, load-bearing\ndifference (verified in practice: a `git \u002F pr workflow` promotion attempt across 6 variants\nfound `co-security` used `\u002Fsync \"security: ...\"` where the others used `\u002Fsync \"feat: ...\"`\n— textually close, semantically not interchangeable).\n\n### 3. Execute a promotion\n\n```bash\nbun scripts\u002Fpromote-context-section.ts \\\n  --heading \"\u003Cheading text, exactly as it appears in audit.ts's output>\" \\\n  --variants co-a,co-b,co-c \\\n  [--source \u003Cvariant>]         # which variant's text becomes canonical (default: first listed)\n  [--after-heading \"\u003Ctext>\"]   # where in docs\u002Fcontext.md to insert (default: before Lifecycle Management)\n  [--dry-run]                  # always run this first\n```\n\nReview the dry-run output — the per-variant content preview and any divergence warnings —\nbefore re-running without `--dry-run`. The script:\n- Inserts the canonical section into `templates\u002Fcommon\u002Fdocs\u002Fcontext.md` and bumps its version footer\n- Removes the section from each listed variant's `templates\u002F\u003Cvariant>\u002Fdocs\u002F\u003Cvariant>.context.md`\n- Does **not** decide anything and does **not** touch already-scaffolded projects (see step 4)\n\n**Fixed 2026-09-22 — nested `###` subsections are no longer dropped.** Earlier versions\nof the tool removed the promoted section with a regex that stopped at the *next* `#{2,3}`\nheading, so if the promoted `##` section had a nested `###` subsection, that subsection was\nexcluded from both the removal (left behind as an orphaned, parent-less duplicate in the\nvariant file) *and* the canonical content copied into `docs\u002Fcontext.md` (never appeared\nthere either) — real content loss if no other copy of that subsection existed elsewhere in\nthe file. Hit in practice promoting \"Scripts\" (`### Hybrid Scripting` nested underneath):\n7 variant files were left with an orphaned duplicate, and `co-consult`\u002F`co-export`\ngenuinely lost the content since neither had a second copy elsewhere. Fixed in\n`promote-context-section.ts` v1.1.0 (nesting-aware spans, `helpers\u002Fcontext-sections.ts`\nv1.6.0): a promoted `##` section now carries its `###` children into `docs\u002Fcontext.md` AND\nremoves them from every variant file; fenced `#` lines never terminate a section. The\ndry-run preview notes when a candidate section includes nested subsections.\n\n### 4. Handle already-scaffolded projects\n\nRemoving a section from `templates\u002F\u003Cvariant>\u002Fdocs\u002F\u003Cvariant>.context.md` only fixes *future*\nscaffolds (`new-project.ts`, `create-l3-scaffold.ts`) and stops `audit.ts` from re-flagging the\n*template*. Existing `Projects\u002F*\u002Fdocs\u002F\u003Cvariant>.context.md` files keep the old duplicated text\n— there is no automated cleanup path for this (the file isn't a managed-block merge target, so\n`upgrade-project.ts` can't safely delete arbitrary content from it). Either:\n- manually remove the now-redundant section from each affected existing project, or\n- accept the duplication there until an unrelated future edit touches that section.\n\nThen, for each existing project of the affected variants, pick up the *promoted* content into\n`docs\u002Fcontext.md`:\n\n```bash\nbun scripts\u002Fupgrade-project.ts \u003Cproject-path> --variant \u003Cvariant> --dry-run\n```\n\n### 5. Extraction path (subset-shared content)\n\nWhen step 2 decides a candidate should become a shared skill instead of promoting to\n`docs\u002Fcontext.md`: create `skills\u002F\u003Cname>\u002FSKILL.md` with the shared content, update the affected\nvariants' `agents\u002Fpm.md` or `AGENTS.md` to reference it, then manually remove the duplicated\nprose from each affected variant's `docs\u002F\u003Cvariant>.context.md` (`promote-context-section.ts`\nonly targets `docs\u002Fcontext.md` as the promotion destination — it's not a general dedup tool for\nskills, since skill placement\u002Fwiring per variant needs its own review).\n\n### 6. Verify and log\n\n```bash\nbun scripts\u002Faudit.ts   # the promoted heading should no longer appear as a candidate\n```\n\nLog the decision and rationale in the session's `memory\u002FYYYY-MM-DD.md` — this is the audit\ntrail ADR-0050 Part 3 relies on for \"why was this promoted\u002Fleft alone\" questions later.\n\n## See Also\n\n- ADR-0050 Part 3 (Variant Script Inheritance and Golden-Reference SSOT — Context Commonization\n  Review) — full rationale, thresholds, and open questions\n- `templates\u002Fcommon\u002Fdocs\u002Fcontext.md` § Lifecycle Management § Context Commonization Review\n- `skills\u002Fupgrade-project\u002FSKILL.md` — how promoted `docs\u002Fcontext.md` content reaches existing projects\n- `skills\u002Fcreate-variant\u002FSKILL.md` — the natural trigger point after scaffolding a new variant\n- `docs\u002Fgovernance\u002Fvariant-contract.md` § Context.md Structure Standard (`validate-templates.ts`\n  Check WS-09) — a related but distinct concern: this skill promotes\u002Fdedups *content* that's\n  duplicated across variants; WS-09 instead enforces that every variant's `docs\u002F\u003Cvariant>.context.md`\n  has the same top-level *structure* (slot presence + order), regardless of whether the content in\n  each slot is shared or variant-specific. Content standardization was explicitly considered and\n  rejected during WS-09's design — see that doc for why.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":35,"description":41,"l2_propagate":19,"last_reviewed":42},"architect","workspace","active","1.1.0",{"type":28,"triggers":29},"process",[30,31,32,33,34],"context commonization review","variant context duplication","commonization review","context.md duplication review","context.md commonization",[36,39],{"type":37,"skill":38},"follows","promote-variant",{"type":37,"skill":40},"meeting-facilitation","Reviews cross-variant docs\u002F\u003Cvariant>.context.md duplication and promotes genuinely shared content into the common docs\u002Fcontext.md (ADR-0050 Part 3). Use when: after scaffolding a new variant, on a periodic cadence (every 5 new variants or quarterly, whichever first), or on-demand when asked to check for or reduce context.md duplication across variants.\n",1794096000000,"main","1162ccc568cf90c01b3886d6143cbfd851a37883","skills\u002Fcontext-commonization-review",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill context-commonization-review",{"tool":57,"command":58},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill context-commonization-review",{"tool":60,"command":61},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill context-commonization-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Fskills\u002Fcontext-commonization-review\u002FSKILL.md",true,[],[66,74,79,84,89,94],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":73},"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":75,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":73},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":80,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":73},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":85,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":73},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":90,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":73},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":95,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":73},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]