[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TSQYBBJ3FG1MSMB9B33SZ":3,"skill-same:01M72TSQYBBJ3FG1MSMB9B33SZ":44},{"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":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72TSQYBBJ3FG1MSMB9B33SZ","ws-tdd-review",null,"Audit existing test code for quality, depth, and adherence to TDD principles.","vempio\u002FWhittleSpec","vempio","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F226084226?v=4","01M72TQW11B57V5ZE8MQPKJ5QY","01M72TQW22F5C4SJ317ETCWHFW",4,"MIT","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.review\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ws-tdd-review\ndescription: Audit existing test code for quality, depth, and adherence to TDD principles.\n---\n# ws.tdd.review\n\nLoad shared context: `ws.tdd._meta\u002FSKILL.md` — the sibling skill in the same skills directory this skill loaded from (resolves under any clone name, install location, or skills-root override). Also load: `ws.tdd._meta\u002Ftest-quality-checklist.md` (step 3's criteria) and `ws.tdd._meta\u002Fdebt-protocol.md` (the debt scan that opens it).\n\n## Purpose\n\nReview existing test code against TDD quality standards. Distinct from `\u002Fws.review` (reviews **specifications** for testability) -- this reviews **actual test code** for quality.\n\n## Process\n\n### 1. Scope\n\nAsk: \"Which test files or modules should I review?\" (or confirm if specified).\n\n### 2. Depth\n\n**Default: thorough.** Examine every test file in scope, read each test function. Most common complaint: superficial review missing issues careful reading would catch.\n\nIf scope large (> 20 files), state and propose batching: \"N files in scope. I'll review in batches of 8, starting with [area].\"\n\n### 3. Evaluate\n\nWork through `ws.tdd._meta\u002Ftest-quality-checklist.md`, against\n`ws.tdd._meta\u002FSKILL.md` § Quality Standards. The criteria and the adversarial pass both\nlive in that file, so this skill and `ws.fix` hold one bar rather than two paraphrases\nof it.\n\nThe adversarial pass is not optional. A checklist run without it reports what the tests\nsay; it does not establish that they would catch a wrong implementation.\n\n### 4. Report\n\n```markdown\n## Test Quality Review: [scope]\n\n### Summary\n\n- **Files reviewed**: [count]\n- **Tests reviewed**: [count]\n- **Critical issues**: [count] (success theater, broken assertions)\n- **Improvements**: [count] (depth, structure, documentation)\n\n### Critical Issues\n\n[Tests not actually validating anything, including untested state clearing paths]\n\n- [File:line] `test_name`: [what's wrong, why it matters]\n\n### Depth Issues\n\n[Assertions checking too shallowly]\n\n- [File:line] `test_name`: checks [what it checks], should check [what it should check]\n\n### Structural Issues\n\n[AAA violations, lumped behaviors, poor naming]\n\n### Dead Code & Usage\n\n- [File:line] `function_name`: defined and tested but never called from production flow\n\n### Test Level\n\n- [File:line] `test_name`: unit-tests coordination logic, should be integration-tested (or vice versa)\n\n### BDD Quality (when .feature files exist)\n\n- [File:line] `scenario_name`: [what's wrong]\n\n### Task Completion Audit (when task file and .feature files exist)\n\n| Scenario | Task | Task Status | Scenario Status | Finding |\n|----------|------|-------------|-----------------|---------|\n| Generate pending certs | 2b | [x] | active | OK |\n| Field validation x3 | 2a | [x] | @todo | CRITICAL: task claims done |\n| Send with attachment | 3a | [~] | active | OK (in progress) |\n| Full pipeline | -- | -- | @todo | Orphan: no task claims this |\n\n- **Critical**: [count] scenarios still @todo under completed tasks\n- **Orphans**: [count] scenarios not traced to any task\n- **Pending**: [count] scenarios awaiting activation for incomplete tasks\n\n### BDD-Documentation Correspondence (when operator docs and .feature files exist)\n\n- **Documented workflows without BDD**: [list workflow steps with no matching scenario]\n- **BDD scenarios without documentation**: [list scenarios exercising undocumented workflows]\n- **CLI usability gaps**: [missing @cli scenarios for --help, unknown subcommand]\n\n### Traceability (when SDD context available)\n\n- **Criteria with tests**: [list with AC identifiers]\n- **Criteria without tests**: [list -- these need `\u002Fws.tdd.idea`]\n- **Tests without AC reference**: [list -- typically fine; flag only if scope creep]\n\n### Recommendations\n\n[Prioritized list, most impactful first]\n```\n\n## Output\n\nReport following template above, delivered for discussion. Report is conversation starter, not final verdict -- human may disagree with severity or priorities.\n\n## Relationship to `\u002Fws.review`\n\nComplementary: `\u002Fws.review` reviews **specifications** for testability. `\u002Fws.tdd.review` reviews **actual test code** for quality. Both invoked by `\u002Fws.fix` during quality passes.\n\n## Anti-Patterns\n\n- Reviewing spec testability (that's `\u002Fws.review`)\n- Suggesting new tests to write (that's `\u002Fws.tdd.idea`)\n- Rewriting tests during review (review first, fix separately)\n","# ws.tdd.review\n\nLoad shared context: `ws.tdd._meta\u002FSKILL.md` — the sibling skill in the same skills directory this skill loaded from (resolves under any clone name, install location, or skills-root override). Also load: `ws.tdd._meta\u002Ftest-quality-checklist.md` (step 3's criteria) and `ws.tdd._meta\u002Fdebt-protocol.md` (the debt scan that opens it).\n\n## Purpose\n\nReview existing test code against TDD quality standards. Distinct from `\u002Fws.review` (reviews **specifications** for testability) -- this reviews **actual test code** for quality.\n\n## Process\n\n### 1. Scope\n\nAsk: \"Which test files or modules should I review?\" (or confirm if specified).\n\n### 2. Depth\n\n**Default: thorough.** Examine every test file in scope, read each test function. Most common complaint: superficial review missing issues careful reading would catch.\n\nIf scope large (> 20 files), state and propose batching: \"N files in scope. I'll review in batches of 8, starting with [area].\"\n\n### 3. Evaluate\n\nWork through `ws.tdd._meta\u002Ftest-quality-checklist.md`, against\n`ws.tdd._meta\u002FSKILL.md` § Quality Standards. The criteria and the adversarial pass both\nlive in that file, so this skill and `ws.fix` hold one bar rather than two paraphrases\nof it.\n\nThe adversarial pass is not optional. A checklist run without it reports what the tests\nsay; it does not establish that they would catch a wrong implementation.\n\n### 4. Report\n\n```markdown\n## Test Quality Review: [scope]\n\n### Summary\n\n- **Files reviewed**: [count]\n- **Tests reviewed**: [count]\n- **Critical issues**: [count] (success theater, broken assertions)\n- **Improvements**: [count] (depth, structure, documentation)\n\n### Critical Issues\n\n[Tests not actually validating anything, including untested state clearing paths]\n\n- [File:line] `test_name`: [what's wrong, why it matters]\n\n### Depth Issues\n\n[Assertions checking too shallowly]\n\n- [File:line] `test_name`: checks [what it checks], should check [what it should check]\n\n### Structural Issues\n\n[AAA violations, lumped behaviors, poor naming]\n\n### Dead Code & Usage\n\n- [File:line] `function_name`: defined and tested but never called from production flow\n\n### Test Level\n\n- [File:line] `test_name`: unit-tests coordination logic, should be integration-tested (or vice versa)\n\n### BDD Quality (when .feature files exist)\n\n- [File:line] `scenario_name`: [what's wrong]\n\n### Task Completion Audit (when task file and .feature files exist)\n\n| Scenario | Task | Task Status | Scenario Status | Finding |\n|----------|------|-------------|-----------------|---------|\n| Generate pending certs | 2b | [x] | active | OK |\n| Field validation x3 | 2a | [x] | @todo | CRITICAL: task claims done |\n| Send with attachment | 3a | [~] | active | OK (in progress) |\n| Full pipeline | -- | -- | @todo | Orphan: no task claims this |\n\n- **Critical**: [count] scenarios still @todo under completed tasks\n- **Orphans**: [count] scenarios not traced to any task\n- **Pending**: [count] scenarios awaiting activation for incomplete tasks\n\n### BDD-Documentation Correspondence (when operator docs and .feature files exist)\n\n- **Documented workflows without BDD**: [list workflow steps with no matching scenario]\n- **BDD scenarios without documentation**: [list scenarios exercising undocumented workflows]\n- **CLI usability gaps**: [missing @cli scenarios for --help, unknown subcommand]\n\n### Traceability (when SDD context available)\n\n- **Criteria with tests**: [list with AC identifiers]\n- **Criteria without tests**: [list -- these need `\u002Fws.tdd.idea`]\n- **Tests without AC reference**: [list -- typically fine; flag only if scope creep]\n\n### Recommendations\n\n[Prioritized list, most impactful first]\n```\n\n## Output\n\nReport following template above, delivered for discussion. Report is conversation starter, not final verdict -- human may disagree with severity or priorities.\n\n## Relationship to `\u002Fws.review`\n\nComplementary: `\u002Fws.review` reviews **specifications** for testability. `\u002Fws.tdd.review` reviews **actual test code** for quality. Both invoked by `\u002Fws.fix` during quality passes.\n\n## Anti-Patterns\n\n- Reviewing spec testability (that's `\u002Fws.review`)\n- Suggesting new tests to write (that's `\u002Fws.tdd.idea`)\n- Rewriting tests during review (review first, fix separately)\n",{"name":5,"description":7},"main","1ad262fc695612ff484ee364ff66ab5298bdda58","skills\u002Fws.tdd.review",0,"https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec","https:\u002F\u002Fgithub.com\u002Fvempio","2026-10-06 16:08:48",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add vempio\u002FWhittleSpec --skill ws-tdd-review",{"tool":36,"command":37},"bunx","bunx skills add vempio\u002FWhittleSpec --skill ws-tdd-review",{"tool":39,"command":40},"pnpm","pnpm dlx skills add vempio\u002FWhittleSpec --skill ws-tdd-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.review\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M72TSN33MN2J0CW29MBY4WC4","ws-tdd-red","Phase 3 -- implement failing tests, validating assertion quality and depth.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.red\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M72TSJMTHFVC8FW2BGQ0NYD7","ws-tdd-outline","Phase 2 -- tree-level test design, examining intent and approach per test.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.outline\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M72TSFPHD749CY9KRV66T0RH","ws-tdd-idea","Phase 1 -- forest-level test case discovery, mapping the full problem space.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.idea\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72TSD53VT09VF3EG67KA68E","ws-tdd-green","Phase 4 -- write minimal production code to make failing tests pass.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd.green\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72TS9TXQ9RHYF3VBGR87BF6","ws-tdd-meta","TDD shared context -- phased protocol, quality standards, and standing instructions for all TDD skills.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.tdd._meta\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72TS76RJ3K1HNGQXJ2S09HT","ws-sweep","Completeness sweep -- exhaustively verify nothing was missed after a change.","https:\u002F\u002Fgithub.com\u002Fvempio\u002FWhittleSpec\u002Fblob\u002Fmain\u002Fskills\u002Fws.sweep\u002FSKILL.md",[],[]]