[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMF6XNZBEZFE19VM0AFKSW":3,"skill-same:01M7DMF6XNZBEZFE19VM0AFKSW":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7DMF6XNZBEZFE19VM0AFKSW","dsh-trim-cot-leakage",null,"Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as \"used to\", \"no longer\", \"this cut\"; stack or review vantage (\"a later PR in this stack\", \"rejected in review\"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.","arzvaak\u002FBharatCode-Harness","arzvaak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F66210729?v=4","01M7DMD1PNVD1R4C473WYBX88X","01M7DMD1QR8H8QQY7FK14KMMRH",0,"MIT","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-trim-cot-leakage\ndescription: Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as \"used to\", \"no longer\", \"this cut\"; stack or review vantage (\"a later PR in this stack\", \"rejected in review\"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.\n---\n\n# Trimming Chain-of-Thought Leakage\n\nChain-of-thought leakage is prose whose vantage is the authoring session rather than the repository: it cites artifacts only that session could see, narrates the change instead of the state, or argues with a reviewer who has left. The fix is never deletion alone when a passage carries factual clauses — restate each so it stands at HEAD, then delete the transcript around it; a passage carrying none (an audit code, control-flow narration) is deleted outright. **REQUIRED BACKGROUND:** [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md) owns the complete-proposition rule this skill applies; the [committed-artifact-citations note](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-08-09-committed-artifact-citations.md) owns the citation rule's rationale. It is guidance, not a script.\n\n## The one test\n\nFor every suspect passage ask: **could a reader at HEAD, with no access to any session transcript, PR thread, or uncommitted draft, resolve every reference and verify every claim?** If no, restate the surviving facts from the repository's vantage and delete the rest. If yes, it is not leakage, however historical it sounds — but resolvability only clears this skill's bar: on current-state surfaces (READMEs, docs, JSDoc) a resolvable change story is still change narration, and class 3 routes it to its sanctioned home.\n\n## Taxonomy\n\n1. **Dead design-session citations** — `(decision 7)`, `(audit C2)`, `design §4.7`, `plan §1.4`, phase labels (`T4`, `W3`, `P-I`), \"the design ledger\", \"(B ruling)\". If the decision has a committed owner, cite it by name and path; otherwise delete the citation and restate its factual clause to stand alone.\n2. **Stack and PR vantage** — \"a later PR in this stack\", \"this PR adds\", \"the previous commit\". State the shipped mechanism or the extension point; deferred work moves to a `TODO` marker or an issue reference.\n3. **Change narration and version stamps** — \"used to\", \"no longer\", \"the old X\", and indexical stamps (\"v1\", \"this cut\", \"today\", \"now\" contrasting with a past state). State the present behavior; a fixed regression becomes a present-tense counterfactual (\"without X, Y happens\"), never repo history (\"used to Y\").\n4. **Review choreography** — \"Rejected in review:\", \"the reviewer confirmed\", draft ordinals (\"v5 of this note\"), round attributions. Keep the surviving decision and rationale as plain fact; delete who said it when.\n5. **Reviewer-addressed justification** — \"the cast is safe — it simply…\", \"this is correct because…\". A comment arguing its own correctness addresses a reviewer, not a maintainer. State the invariant that makes the code safe, or delete the comment if the code shows it.\n6. **Restatement and derivation transcripts** — control-flow narration (\"first we X, then we Y\"), test walkthroughs, proofs of obvious branches. Delete; keep only a non-obvious contract or invariant.\n7. **Hedges and planning residue** — \"probably fine for now\", \"should be enough\", deferrals with no marker. Promote to `TODO`\u002F`FIXME` or restate as the actual bound; delete the hedge.\n8. **Authoring-language slips** — untranslated working-language fragments (端, 设计稿, `---- 私有 ----` separators) in prose whose language is otherwise English, or the reverse in a zh counterpart. Translate or delete.\n\n## What is not leakage\n\nUnaided citation passes fail in both directions by deleting durable references and keeping dead ones. Apply these keep rules as written; [examples](references\u002Fexamples.md) calibrates each:\n\n- **Issue references** — `#1470`, `TODO(name):`, \"issue #N owns the follow-up\" resolve at HEAD; keep them on any surface, including READMEs. Do not relocate them to Agent Notes.\n- **Merged-PR and issue citations inside Agent Notes and postmortems** — sanctioned evidence per the [documentation standard](..\u002F..\u002F..\u002Fdocs\u002FDEVELOPER_GUIDE.md)'s change-story routing.\n- **Suppression justifications** — `oxlint-disable … -- reason`, coverage-ignore reasons, empty-catch explanations are required prose; fix a false reason, never delete it.\n- **Counterfactual-present regression pins** — \"without X, Y happens\", \"a naive X would…\".\n- **Measured bounds** — \"(measured: 512 nests ≈ 0.15s)\" calibrating a constant; the evidence word \"measured\" is load-bearing.\n- **Runtime old\u002Fnew states** — \"the old connection drains before the new one accepts\" is runtime lifecycle, not change history.\n- **Historical stage names inside a note's change-story sections** — \"the first cut shipped X\" is current-state-safe there; indexical stamps (\"this cut\") stay banned everywhere.\n- **External references that resolve outside the repo by design** — standards sections (RFC 9110 §10.1.5), Figma frame names; the §-ban covers uncommitted internal drafts, not external standards or committed docs that own their §-numbering.\n- **Project voice and genre forms** — \"we\" as project voice; a note's Alternatives-considered section.\n\n## Workflow\n\n1. Scope and exclusions per [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md): require an explicit scope; never touch `vendor\u002F` or `.agents\u002Fnotes\u002Farchived\u002F`. Recorded fixtures and snapshots are derivatives, not prose targets: change the owning source or scenario and regenerate them only when an authorized behavior change requires new evidence.\n2. Audit read-only first: run the [recall batteries](references\u002Frecall-batteries.md) (with `--hidden` so `.agents\u002F` is searched), calibrating each probe against a known positive and a near-miss negative before trusting its output, then judge every hit semantically. The batteries are probes, not the definition — each review round of the original purge found cases the batteries missed, so also read the densest prose in scope (module JSDoc, READMEs, Agent Notes) without a pattern in hand.\n3. Fix owner-first per surface: generated catalogs → trace every consumer, fix the source JSDoc or generator template, then regenerate all derivatives; type-equivalence fences → fix the source JSDoc, then re-paste both bilingual pages (`verify-type-equiv` pins them); bilingual prose → update the counterpart minimally and re-record it through the [lightweight routine](..\u002F..\u002F..\u002Fdocs\u002FDEVELOPER_GUIDE.md#writing-rules); bilingual fences → copy the corrected verbatim block byte-for-byte into both sides per [dsh-doc](..\u002Fdsh-doc\u002FSKILL.md), then re-record the pair; model- or user-visible strings → route through [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md) and change only with owning behavior evidence, otherwise leave unchanged and report the deferral.\n4. Before deleting anything, enumerate the passage's propositions (prose-standard) and check the [overcorrection traps](references\u002Fexamples.md#overcorrection-traps): trims that flip an obligation into an endorsement, promote a hypothetical to a shipped feature, delete a true fact, or drop the evidence source.\n5. Verify: re-run the batteries expecting only sanctioned keeps, this skill's own directory, and the owning note's quoted evidence; confirm every remaining citation resolves at HEAD; run the gates for touched surfaces (`doc-sync` for docs, `verify-type-equiv`, `verify-translation-pairing`).\n","# Trimming Chain-of-Thought Leakage\n\nChain-of-thought leakage is prose whose vantage is the authoring session rather than the repository: it cites artifacts only that session could see, narrates the change instead of the state, or argues with a reviewer who has left. The fix is never deletion alone when a passage carries factual clauses — restate each so it stands at HEAD, then delete the transcript around it; a passage carrying none (an audit code, control-flow narration) is deleted outright. **REQUIRED BACKGROUND:** [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md) owns the complete-proposition rule this skill applies; the [committed-artifact-citations note](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-08-09-committed-artifact-citations.md) owns the citation rule's rationale. It is guidance, not a script.\n\n## The one test\n\nFor every suspect passage ask: **could a reader at HEAD, with no access to any session transcript, PR thread, or uncommitted draft, resolve every reference and verify every claim?** If no, restate the surviving facts from the repository's vantage and delete the rest. If yes, it is not leakage, however historical it sounds — but resolvability only clears this skill's bar: on current-state surfaces (READMEs, docs, JSDoc) a resolvable change story is still change narration, and class 3 routes it to its sanctioned home.\n\n## Taxonomy\n\n1. **Dead design-session citations** — `(decision 7)`, `(audit C2)`, `design §4.7`, `plan §1.4`, phase labels (`T4`, `W3`, `P-I`), \"the design ledger\", \"(B ruling)\". If the decision has a committed owner, cite it by name and path; otherwise delete the citation and restate its factual clause to stand alone.\n2. **Stack and PR vantage** — \"a later PR in this stack\", \"this PR adds\", \"the previous commit\". State the shipped mechanism or the extension point; deferred work moves to a `TODO` marker or an issue reference.\n3. **Change narration and version stamps** — \"used to\", \"no longer\", \"the old X\", and indexical stamps (\"v1\", \"this cut\", \"today\", \"now\" contrasting with a past state). State the present behavior; a fixed regression becomes a present-tense counterfactual (\"without X, Y happens\"), never repo history (\"used to Y\").\n4. **Review choreography** — \"Rejected in review:\", \"the reviewer confirmed\", draft ordinals (\"v5 of this note\"), round attributions. Keep the surviving decision and rationale as plain fact; delete who said it when.\n5. **Reviewer-addressed justification** — \"the cast is safe — it simply…\", \"this is correct because…\". A comment arguing its own correctness addresses a reviewer, not a maintainer. State the invariant that makes the code safe, or delete the comment if the code shows it.\n6. **Restatement and derivation transcripts** — control-flow narration (\"first we X, then we Y\"), test walkthroughs, proofs of obvious branches. Delete; keep only a non-obvious contract or invariant.\n7. **Hedges and planning residue** — \"probably fine for now\", \"should be enough\", deferrals with no marker. Promote to `TODO`\u002F`FIXME` or restate as the actual bound; delete the hedge.\n8. **Authoring-language slips** — untranslated working-language fragments (端, 设计稿, `---- 私有 ----` separators) in prose whose language is otherwise English, or the reverse in a zh counterpart. Translate or delete.\n\n## What is not leakage\n\nUnaided citation passes fail in both directions by deleting durable references and keeping dead ones. Apply these keep rules as written; [examples](references\u002Fexamples.md) calibrates each:\n\n- **Issue references** — `#1470`, `TODO(name):`, \"issue #N owns the follow-up\" resolve at HEAD; keep them on any surface, including READMEs. Do not relocate them to Agent Notes.\n- **Merged-PR and issue citations inside Agent Notes and postmortems** — sanctioned evidence per the [documentation standard](..\u002F..\u002F..\u002Fdocs\u002FDEVELOPER_GUIDE.md)'s change-story routing.\n- **Suppression justifications** — `oxlint-disable … -- reason`, coverage-ignore reasons, empty-catch explanations are required prose; fix a false reason, never delete it.\n- **Counterfactual-present regression pins** — \"without X, Y happens\", \"a naive X would…\".\n- **Measured bounds** — \"(measured: 512 nests ≈ 0.15s)\" calibrating a constant; the evidence word \"measured\" is load-bearing.\n- **Runtime old\u002Fnew states** — \"the old connection drains before the new one accepts\" is runtime lifecycle, not change history.\n- **Historical stage names inside a note's change-story sections** — \"the first cut shipped X\" is current-state-safe there; indexical stamps (\"this cut\") stay banned everywhere.\n- **External references that resolve outside the repo by design** — standards sections (RFC 9110 §10.1.5), Figma frame names; the §-ban covers uncommitted internal drafts, not external standards or committed docs that own their §-numbering.\n- **Project voice and genre forms** — \"we\" as project voice; a note's Alternatives-considered section.\n\n## Workflow\n\n1. Scope and exclusions per [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md): require an explicit scope; never touch `vendor\u002F` or `.agents\u002Fnotes\u002Farchived\u002F`. Recorded fixtures and snapshots are derivatives, not prose targets: change the owning source or scenario and regenerate them only when an authorized behavior change requires new evidence.\n2. Audit read-only first: run the [recall batteries](references\u002Frecall-batteries.md) (with `--hidden` so `.agents\u002F` is searched), calibrating each probe against a known positive and a near-miss negative before trusting its output, then judge every hit semantically. The batteries are probes, not the definition — each review round of the original purge found cases the batteries missed, so also read the densest prose in scope (module JSDoc, READMEs, Agent Notes) without a pattern in hand.\n3. Fix owner-first per surface: generated catalogs → trace every consumer, fix the source JSDoc or generator template, then regenerate all derivatives; type-equivalence fences → fix the source JSDoc, then re-paste both bilingual pages (`verify-type-equiv` pins them); bilingual prose → update the counterpart minimally and re-record it through the [lightweight routine](..\u002F..\u002F..\u002Fdocs\u002FDEVELOPER_GUIDE.md#writing-rules); bilingual fences → copy the corrected verbatim block byte-for-byte into both sides per [dsh-doc](..\u002Fdsh-doc\u002FSKILL.md), then re-record the pair; model- or user-visible strings → route through [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md) and change only with owning behavior evidence, otherwise leave unchanged and report the deferral.\n4. Before deleting anything, enumerate the passage's propositions (prose-standard) and check the [overcorrection traps](references\u002Fexamples.md#overcorrection-traps): trims that flip an obligation into an endorsement, promote a hypothetical to a shipped feature, delete a true fact, or drop the evidence source.\n5. Verify: re-run the batteries expecting only sanctioned keeps, this skill's own directory, and the owning note's quoted evidence; confirm every remaining citation resolves at HEAD; run the gates for touched surfaces (`doc-sync` for docs, `verify-type-equiv`, `verify-translation-pairing`).\n",{"name":5,"description":7},"implementation\u002Fcore-extension-store","091701ca5a621697bf357a7eb654d699468c6200",".agents\u002Fskills\u002Fdsh-trim-cot-leakage","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness","https:\u002F\u002Farzvaak.github.io\u002FBharatCode-Harness\u002F","https:\u002F\u002Fgithub.com\u002Farzvaak","2026-11-07 04:07:44",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add arzvaak\u002FBharatCode-Harness --skill dsh-trim-cot-leakage",{"tool":36,"command":37},"bunx","bunx skills add arzvaak\u002FBharatCode-Harness --skill dsh-trim-cot-leakage",{"tool":39,"command":40},"pnpm","pnpm dlx skills add arzvaak\u002FBharatCode-Harness --skill dsh-trim-cot-leakage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fexamples.md","REFERENCE","参考文档",12566,"https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002Freferences\u002Fexamples.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Frecall-batteries.md",5041,"https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002F.agents\u002Fskills\u002Fdsh-trim-cot-leakage\u002Freferences\u002Frecall-batteries.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7DMGTGVNV395QREH8KYS1WJ","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7DMGRX3R4BGDKH3B6S5XBBC","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7DMGNPK8FC86W4PK3WY28JX","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fmodel-only-skill\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7DMGFS8TJQJN069912Q3CAH","office-xlsx","Read, create, and modify Excel workbooks (.xlsx), including data, formulas, formatting, and pandas analysis. Use for Excel inputs or deliverables. Load before running Office commands. Data and formula tasks skip visual inspection; inspect only for formatting or layout needs. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-xlsx\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7DMGB0TGZWF0Y857P7803ZB","office-pptx","Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts. Use when a PPTX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-pptx\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7DMG6VBMAW4Q5BRDR1PBP03","office-docx","Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables. Use when a DOCX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002Farzvaak\u002FBharatCode-Harness\u002Fblob\u002Fimplementation\u002Fcore-extension-store\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-docx\u002FSKILL.md",[],[]]