[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EHM3Z7JM36BCPJAQBVAMJ1":3,"skill-same:01M7EHM3Z7JM36BCPJAQBVAMJ1":46},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7EHM3Z7JM36BCPJAQBVAMJ1","tdd",null,"Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","renefatuaki\u002Fskills","renefatuaki","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43519979?v=4","01M7EHD24GFMFZRH3Z04WSYC9A","René","01M7EHD25408DH8QKN61CSDXX4",0,"MIT","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftdd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tdd\ndescription: \"Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.\"\ndisable-model-invocation: true\nargument-hint: \"[bug]\"\n---\n\n# TDD Bug Fix\n\nWhen fixing a bug with a clear, cheap test path, make the broken behavior executable before changing production code. The goal is a focused regression test that fails before the fix and passes after it.\n\nDo not force a test when it would be impractical. If the available test would require broad harness setup, brittle mocks, slow end-to-end infrastructure, production-only state, vague reproduction steps, or large unrelated fixture churn, skip adding a new test and use the closest useful verification instead.\n\n## Workflow\n\n1. **Understand the bug.** Identify the intended behavior, current behavior, affected path, and smallest observable reproduction.\n2. **Choose the narrowest executable check.** Prefer the closest unit, component, integration, or regression test already used for that codepath. If no practical test path is obvious, do not create one from scratch just to satisfy the workflow.\n3. **Write the failing test first.** Add the smallest focused test that would have caught the bug. The test should encode intended behavior, not mirror the current implementation.\n4. **Run the new test before fixing.** Confirm it fails for the intended reason. If it passes or fails for an unrelated reason, correct the test or reproduction before editing the implementation.\n5. **Fix the bug.** Make the smallest production change that satisfies the intended behavior while preserving nearby contracts.\n6. **Rerun the regression test.** Confirm the test now passes.\n\n## If a Failing Test Is Impractical\n\nUse the closest executable regression check instead: a targeted script, manual reproduction command, browser automation, snapshot comparison, log assertion, or focused integration check.\n\nPrefer no new test over a bad test. A bad test is one that mostly tests mocks, encodes current implementation details, depends on timing or unrelated global state, needs expensive infrastructure for a small fix, or would be deleted immediately after proving the fix.\n\n## Guardrails\n\n- Do not change tests merely to match a wrong implementation.\n- Do not weaken existing assertions unless the expected behavior has genuinely changed and the reason is clear.\n- Keep the regression test focused on the bug. Avoid broad fixture churn or unrelated coverage expansion.\n- If the bug is flaky, make the test deterministic where possible and document the signal being locked down.\n- If the bug exposes a broader class of failures, first land the focused regression path, then consider additional sibling coverage.\n\n## Final Response\n\nReport the evidence, not just the outcome:\n\n- Name the failing-before test or executable check and the failure it produced.\n- Name the passing-after test run and any nearby validation performed.\n- If failing-before evidence could not be demonstrated, state why and describe the closest regression check used instead.\n","# TDD Bug Fix\n\nWhen fixing a bug with a clear, cheap test path, make the broken behavior executable before changing production code. The goal is a focused regression test that fails before the fix and passes after it.\n\nDo not force a test when it would be impractical. If the available test would require broad harness setup, brittle mocks, slow end-to-end infrastructure, production-only state, vague reproduction steps, or large unrelated fixture churn, skip adding a new test and use the closest useful verification instead.\n\n## Workflow\n\n1. **Understand the bug.** Identify the intended behavior, current behavior, affected path, and smallest observable reproduction.\n2. **Choose the narrowest executable check.** Prefer the closest unit, component, integration, or regression test already used for that codepath. If no practical test path is obvious, do not create one from scratch just to satisfy the workflow.\n3. **Write the failing test first.** Add the smallest focused test that would have caught the bug. The test should encode intended behavior, not mirror the current implementation.\n4. **Run the new test before fixing.** Confirm it fails for the intended reason. If it passes or fails for an unrelated reason, correct the test or reproduction before editing the implementation.\n5. **Fix the bug.** Make the smallest production change that satisfies the intended behavior while preserving nearby contracts.\n6. **Rerun the regression test.** Confirm the test now passes.\n\n## If a Failing Test Is Impractical\n\nUse the closest executable regression check instead: a targeted script, manual reproduction command, browser automation, snapshot comparison, log assertion, or focused integration check.\n\nPrefer no new test over a bad test. A bad test is one that mostly tests mocks, encodes current implementation details, depends on timing or unrelated global state, needs expensive infrastructure for a small fix, or would be deleted immediately after proving the fix.\n\n## Guardrails\n\n- Do not change tests merely to match a wrong implementation.\n- Do not weaken existing assertions unless the expected behavior has genuinely changed and the reason is clear.\n- Keep the regression test focused on the bug. Avoid broad fixture churn or unrelated coverage expansion.\n- If the bug is flaky, make the test deterministic where possible and document the signal being locked down.\n- If the bug exposes a broader class of failures, first land the focused regression path, then consider additional sibling coverage.\n\n## Final Response\n\nReport the evidence, not just the outcome:\n\n- Name the failing-before test or executable check and the failure it produced.\n- Name the passing-after test run and any nearby validation performed.\n- If failing-before evidence could not be demonstrated, state why and describe the closest regression check used instead.\n",{"name":5,"description":7,"argument-hint":24,"disable-model-invocation":25},"[bug]",true,"main","95608c3222b36a55dba667cf51a92a2efdf5e65c","skills\u002Fworkflow\u002Ftdd","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills","https:\u002F\u002Fgithub.com\u002Frenefatuaki","Senior Software Engineer","2026-11-11 02:18:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add renefatuaki\u002Fskills --skill tdd",{"tool":39,"command":40},"bunx","bunx skills add renefatuaki\u002Fskills --skill tdd",{"tool":42,"command":43},"pnpm","pnpm dlx skills add renefatuaki\u002Fskills --skill tdd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftdd\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EHM6WHPXSSEDBK04TSGYW3","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7EHM0WJND99F23YC24X0PXS","swarm","Fan out N parallel workers, drain them, and return one report. Use for \u002Fswarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fswarm\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7EHKXJPJHD57W7S0V2FYAAM","show-me-your-work","Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for \u002Fshow-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fshow-me-your-work\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EHKSX411XWSR4GYZ9VKP42","interrogate","Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Finterrogate\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EHKPW39MGDZHA95BKXK5NJ","how","Use for \"how does X work\", code walkthroughs before changing something, and placement \u002F ownership \u002F layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fhow\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EHKM1V0FKQEMQ4ZEZEC4G3","figure-it-out","Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use for \u002Ffigure-it-out or 'figure it out'.","https:\u002F\u002Fgithub.com\u002Frenefatuaki\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ffigure-it-out\u002FSKILL.md",[],[]]