[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQ48XK94BYRMQVDCQRTY77":3,"skill-same:01M7CQ48XK94BYRMQVDCQRTY77":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CQ48XK94BYRMQVDCQRTY77","testing-craft",null,"Provides Google-derived testing strategy, test-writing craft, and test-suite health reference, distilled from Software Engineering at Google (the Flamingo book), the Google Testing Blog, and Google's published testing-infrastructure research. Canon's `reviewer` subagent reads the writing-craft and strategy references as review criteria. Invoke directly to design a test strategy, audit an existing suite's health, or triage a flaky or brittle test.","urban233\u002FCanon","urban233","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81388165?v=4","01M7CPZG1XX0BZ1KTRAJWTGWFH","Martin Urban","01M7CPZG2JPZEX3EJEG98XGTA7",1,"BSD-3-Clause","https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Ftesting-craft\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: testing-craft\ndescription: Provides Google-derived testing strategy, test-writing craft, and test-suite health reference, distilled from Software Engineering at Google (the Flamingo book), the Google Testing Blog, and Google's published testing-infrastructure research. Canon's `reviewer` subagent reads the writing-craft and strategy references as review criteria. Invoke directly to design a test strategy, audit an existing suite's health, or triage a flaky or brittle test.\n---\n\n# Testing Craft\n\nReference for designing a test strategy, writing individual tests well,\nand keeping a test suite healthy over time -- distilled from Google's\npublic testing methodology (*Software Engineering at Google*, the Google\nTesting Blog, and Google's peer-reviewed testing-infrastructure research).\nThis skill has no template of its own; it sharpens test content another\nskill or agent is already producing.\n\n## Invocation boundary\n\nUse this skill in two situations:\n\n- **As a prerequisite.** Canon's `reviewer` subagent reads\n  `references\u002Fwriting-tests.md` and `references\u002Ftest-strategy.md` as its\n  review criteria for a change's tests. That's a read, not a full\n  invocation of this skill -- continue in the calling agent's own\n  workflow.\n- **Directly**, when the developer asks to design a test strategy for a\n  change, audit an existing test suite's health, triage a specific flaky\n  or brittle test, or asks for this skill by name.\n\n## Apply the references\n\n- `references\u002Ftest-strategy.md` -- size vs. scope, the target test-count\n  pyramid and its antipatterns, when a larger test earns its cost, and the\n  coverage-decision heuristic. Read before deciding *what* to test and at\n  what level.\n- `references\u002Fwriting-tests.md` -- DAMP over DRY for test code, behavior-\n  named tests, the test-doubles priority ladder, and the brittleness\n  checklist. Read before writing or revising an individual test.\n- `references\u002Ftest-suite-health.md` -- hermetic tests, flaky-test triage,\n  and coverage-as-diagnostic. Read before auditing or maintaining an\n  existing suite.\n\nEach reference ends in a self-check list; run it against the test\ncontent before treating that content as done.\n\n## When invoked directly\n\n1. Identify which of three cases applies: a new or revised test strategy,\n   a health audit of an existing suite, or triage of one specific flaky or\n   brittle test. Ask if the developer's request is ambiguous between them\n   -- the three use different references and produce different output.\n2. **New or revised strategy.** Gather the change's actual risk and shape\n   (new component, size, blast radius, existing coverage) from the\n   developer's request and the repository itself. Apply\n   `references\u002Ftest-strategy.md` to produce a size\u002Fscope recommendation, a\n   test-doubles approach, and a list of any larger tests that earn their\n   cost -- with the reasoning, not just the list. Hand the result back\n   into the calling skill's own artifact if one is open; otherwise present\n   it directly.\n3. **Suite health audit.** Inspect the existing suite's structure, runtime,\n   and recent CI or test-run history if available. Apply\n   `references\u002Ftest-suite-health.md`'s checklist (hermeticity, flake\n   signal, pyramid shape) and `references\u002Fwriting-tests.md`'s brittleness\n   signals. Report findings ranked by how much trust they erode, each with\n   specific evidence (a flaky test's failure history, a brittle test's\n   coupling to an internal method) -- do not silently rewrite tests as\n   part of an audit; that is separate, explicitly-requested work once the\n   developer accepts a finding.\n4. **Flaky or brittle triage.** Apply `references\u002Ftest-suite-health.md`'s\n   triage decision tree to the specific test named. Recommend one of\n   fix-now, quarantine-and-ticket, or delete, with the reasoning, not a\n   default.\n\n## Handoff\n\nThis skill does not decide product scope, architecture, or which change\nto make -- it only sharpens test content already in scope. Return control\nto the calling skill or the developer once the relevant self-check passes,\nor once a direct invocation's findings are reported.\n","# Testing Craft\n\nReference for designing a test strategy, writing individual tests well,\nand keeping a test suite healthy over time -- distilled from Google's\npublic testing methodology (*Software Engineering at Google*, the Google\nTesting Blog, and Google's peer-reviewed testing-infrastructure research).\nThis skill has no template of its own; it sharpens test content another\nskill or agent is already producing.\n\n## Invocation boundary\n\nUse this skill in two situations:\n\n- **As a prerequisite.** Canon's `reviewer` subagent reads\n  `references\u002Fwriting-tests.md` and `references\u002Ftest-strategy.md` as its\n  review criteria for a change's tests. That's a read, not a full\n  invocation of this skill -- continue in the calling agent's own\n  workflow.\n- **Directly**, when the developer asks to design a test strategy for a\n  change, audit an existing test suite's health, triage a specific flaky\n  or brittle test, or asks for this skill by name.\n\n## Apply the references\n\n- `references\u002Ftest-strategy.md` -- size vs. scope, the target test-count\n  pyramid and its antipatterns, when a larger test earns its cost, and the\n  coverage-decision heuristic. Read before deciding *what* to test and at\n  what level.\n- `references\u002Fwriting-tests.md` -- DAMP over DRY for test code, behavior-\n  named tests, the test-doubles priority ladder, and the brittleness\n  checklist. Read before writing or revising an individual test.\n- `references\u002Ftest-suite-health.md` -- hermetic tests, flaky-test triage,\n  and coverage-as-diagnostic. Read before auditing or maintaining an\n  existing suite.\n\nEach reference ends in a self-check list; run it against the test\ncontent before treating that content as done.\n\n## When invoked directly\n\n1. Identify which of three cases applies: a new or revised test strategy,\n   a health audit of an existing suite, or triage of one specific flaky or\n   brittle test. Ask if the developer's request is ambiguous between them\n   -- the three use different references and produce different output.\n2. **New or revised strategy.** Gather the change's actual risk and shape\n   (new component, size, blast radius, existing coverage) from the\n   developer's request and the repository itself. Apply\n   `references\u002Ftest-strategy.md` to produce a size\u002Fscope recommendation, a\n   test-doubles approach, and a list of any larger tests that earn their\n   cost -- with the reasoning, not just the list. Hand the result back\n   into the calling skill's own artifact if one is open; otherwise present\n   it directly.\n3. **Suite health audit.** Inspect the existing suite's structure, runtime,\n   and recent CI or test-run history if available. Apply\n   `references\u002Ftest-suite-health.md`'s checklist (hermeticity, flake\n   signal, pyramid shape) and `references\u002Fwriting-tests.md`'s brittleness\n   signals. Report findings ranked by how much trust they erode, each with\n   specific evidence (a flaky test's failure history, a brittle test's\n   coupling to an internal method) -- do not silently rewrite tests as\n   part of an audit; that is separate, explicitly-requested work once the\n   developer accepts a finding.\n4. **Flaky or brittle triage.** Apply `references\u002Ftest-suite-health.md`'s\n   triage decision tree to the specific test named. Recommend one of\n   fix-now, quarantine-and-ticket, or delete, with the reasoning, not a\n   default.\n\n## Handoff\n\nThis skill does not decide product scope, architecture, or which change\nto make -- it only sharpens test content already in scope. Return control\nto the calling skill or the developer once the relevant self-check passes,\nor once a direct invocation's findings are reported.\n",{"name":5,"description":7},"main","453e779ab8a331947f8cb2b1168cb0ba8f1f3256","plugins\u002Fcodex\u002Fskills\u002Ftesting-craft",0,"https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon","https:\u002F\u002Fgithub.com\u002Furban233","2026-10-01 06:44:57",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add urban233\u002FCanon --skill testing-craft",{"tool":37,"command":38},"bunx","bunx skills add urban233\u002FCanon --skill testing-craft",{"tool":40,"command":41},"pnpm","pnpm dlx skills add urban233\u002FCanon --skill testing-craft","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Ftesting-craft\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Ftest-strategy.md","REFERENCE","参考文档",6082,"https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Ftesting-craft\u002Freferences\u002Ftest-strategy.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ftest-suite-health.md",5212,"https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Ftesting-craft\u002Freferences\u002Ftest-suite-health.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fwriting-tests.md",4962,"https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Ftesting-craft\u002Freferences\u002Fwriting-tests.md",[60,67,74,80,87,94],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CQ465824PE31REMF8HFB74","ship","Decide whether a change is ready to hand to a human, and open the pull request when it is. Use once the work is done and verified, before opening a PR or telling the developer the change is ready.","https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CQ40YM28KQ9H79HEC2T0SB","review","Dispatch Canon's independent reviewer subagents for this branch and read their verdicts back from canon_review. Use once a change is built and verified, before shipping. This skill only dispatches and reads back -- the review itself runs inside the subagent, in a fresh context, and never in this session.","https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CQ3ZK97QCHFZ7NNP6E1EZP","review-change","https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Freview-change\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CQ3KTVG5BAW4ZVMNYS1AFE","plan","Shape what plan mode drafts, so the plan Canon saves needs no follow-up. Use whenever drafting a plan for approval in plan mode, before writing it to .canon\u002Fplans\u002F.","https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CQ2XHVX3F1GT08CCCY225D","frame","Surface the open questions before planning a multi-branch feature, and shape the feature plan mode drafts. Use before entering plan mode for work that obviously won't fit in one branch and one pull request -- never for a change that already does.","https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fframe\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7CQ24Q1VA2M3R6XBYPN7HT8","decide","Draft and commit a decision record for a design or architecture choice made in this session, once it has survived implementation. Use at ship time, right before opening the pull request, when the branch made a decision worth recording.","https:\u002F\u002Fgithub.com\u002Furban233\u002FCanon\u002Fblob\u002Fmain\u002Fplugins\u002Fcodex\u002Fskills\u002Fdecide\u002FSKILL.md",[],[]]