[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RBR054EB4FMMNN2EEHH13":3,"skill-same:01M77RBR054EB4FMMNN2EEHH13":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M77RBR054EB4FMMNN2EEHH13","testing",null,"Testing workflow and quality standards for writing and running tests.\nUse when: (1) Writing new tests, (2) Adding a new feature that needs tests,\n(3) Modifying logic that has existing tests, (4) Before claiming a task is complete.","finewood2008\u002Fcentaurai-decision","finewood2008","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F212194470?v=4","01M75HGRZJ31P9W3T90VHFS1X8","Finewood","01M77RA40TQ7E0FEMCYQF58BZ4",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftesting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: testing\ndescription: |\n  Testing workflow and quality standards for writing and running tests.\n  Use when: (1) Writing new tests, (2) Adding a new feature that needs tests,\n  (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.\n---\n\n# Testing Skill\n\nStandards and workflow for writing and running tests. Every feature must be tested.\n\n**Announce at start:** \"I'm using testing skill to ensure proper test coverage.\"\n\n## Trigger Conditions\n\n- Writing new tests for a feature or bug fix\n- Adding a new feature (must include tests)\n- Modifying logic that has existing tests (must update them)\n- Before claiming work is complete\n- Before committing code\n\n## Framework\n\n**Vitest 4** — configured in `vitest.config.ts`.\n\n## Test Structure\n\n```\ntests\u002F\n├── unit\u002F          # Individual functions, utilities, components\n├── integration\u002F   # IPC, database, service interactions\n├── regression\u002F    # Regression test cases\n└── e2e\u002F           # End-to-end tests (Playwright, playwright.config.ts)\n```\n\n## Two Test Environments\n\n| Environment      | When                              | File naming     |\n| ---------------- | --------------------------------- | --------------- |\n| `node` (default) | Main process, utilities, services | `*.test.ts`     |\n| `jsdom`          | DOM\u002Fbrowser-dependent code        | `*.dom.test.ts` |\n\n## Workflow\n\n### Step 1: Identify What to Test\n\nBefore writing tests, list the **riskiest scenarios** first:\n\n- What happens when the dependency returns `undefined` \u002F throws?\n- What happens at boundaries (empty list, max retries, past timestamp)?\n- What is most likely to break in production?\n\n### Step 2: Write Tests\n\nFollow these quality rules:\n\n**1. Describe behavior, not code structure**\n\n```typescript\n\u002F\u002F Wrong — describes implementation\nit('should call repo.getConversation', ...)\n\n\u002F\u002F Correct — describes behavior\nit('should return cached task without hitting repo on second call', ...)\nit('should reject with error when conversation does not exist', ...)\n```\n\n**2. Every describe block must cover at least one failure path**\n\nHappy-path-only tests leave the most dangerous code untested.\n\n**3. One behavior per test**\n\nKeep each `it()` focused. More than 3 `expect()` calls in one test is a signal it is testing too much at once.\n\n**4. Self-check**\n\nAfter writing a test, mentally delete the core logic it targets. If the test would still pass, rewrite it — it is not guarding anything.\n\n**5. Start from risk, not from coverage gaps**\n\nList scenarios most likely to produce bugs. Write those first. Coverage is the outcome, not the starting point.\n\n### Step 3: Run Tests\n\n```bash\nbun run test              # Run all tests (REQUIRED before every commit)\nbun run test:coverage     # Check coverage (before opening a PR)\n```\n\n### Step 4: Verify Coverage\n\n**Coverage target**: ≥ 80% for all source files matched by `vitest.config.ts` → `coverage.include` (currently `src\u002F**\u002F*.{ts,tsx}` plus a few scripts).\n\nNew source files are automatically included in coverage — no manual config changes needed. If a new file is accidentally excluded by a rule in `coverage.exclude`, remove it from the exclude list.\n\n### Step 5: Update Existing Tests\n\nWhen modifying logic, check if existing tests need updating:\n\n```bash\nbun run test -- --reporter=verbose   # See which tests pass\u002Ffail with names\n```\n\nIf a test fails because the behavior changed intentionally, update the test. If it fails unexpectedly, investigate.\n\n## Edge Case Checklist\n\nWhen testing a module, verify:\n\n- [ ] `null` \u002F `undefined` inputs handled\n- [ ] Empty arrays\u002Fobjects handled\n- [ ] Error thrown by dependencies handled\n- [ ] Boundary values (0, -1, max, empty string)\n- [ ] Async operations (timeout, rejection, cancellation)\n\n## Quick Checklist\n\nBefore submitting code:\n\n- [ ] New features have corresponding test cases\n- [ ] Modified logic has updated tests\n- [ ] `bun run test` passes\n- [ ] Tests describe **behavior**, not implementation\n- [ ] At least one failure path per describe block\n- [ ] New source files are not accidentally excluded by `coverage.exclude`\n- [ ] `bun run test:coverage` meets ≥ 80% target\n\n## Common Mistakes\n\n| Mistake                           | Correct                                       |\n| --------------------------------- | --------------------------------------------- |\n| Testing implementation details    | Test observable behavior                      |\n| Only testing happy path           | Must include at least one failure path        |\n| 5+ expects in one `it()`          | Split into separate tests                     |\n| Skipping tests for \"simple\" code  | Simple code breaks too — test the risky parts |\n| Writing tests after saying \"done\" | Tests are part of \"done\", not an afterthought |\n","# Testing Skill\n\nStandards and workflow for writing and running tests. Every feature must be tested.\n\n**Announce at start:** \"I'm using testing skill to ensure proper test coverage.\"\n\n## Trigger Conditions\n\n- Writing new tests for a feature or bug fix\n- Adding a new feature (must include tests)\n- Modifying logic that has existing tests (must update them)\n- Before claiming work is complete\n- Before committing code\n\n## Framework\n\n**Vitest 4** — configured in `vitest.config.ts`.\n\n## Test Structure\n\n```\ntests\u002F\n├── unit\u002F          # Individual functions, utilities, components\n├── integration\u002F   # IPC, database, service interactions\n├── regression\u002F    # Regression test cases\n└── e2e\u002F           # End-to-end tests (Playwright, playwright.config.ts)\n```\n\n## Two Test Environments\n\n| Environment      | When                              | File naming     |\n| ---------------- | --------------------------------- | --------------- |\n| `node` (default) | Main process, utilities, services | `*.test.ts`     |\n| `jsdom`          | DOM\u002Fbrowser-dependent code        | `*.dom.test.ts` |\n\n## Workflow\n\n### Step 1: Identify What to Test\n\nBefore writing tests, list the **riskiest scenarios** first:\n\n- What happens when the dependency returns `undefined` \u002F throws?\n- What happens at boundaries (empty list, max retries, past timestamp)?\n- What is most likely to break in production?\n\n### Step 2: Write Tests\n\nFollow these quality rules:\n\n**1. Describe behavior, not code structure**\n\n```typescript\n\u002F\u002F Wrong — describes implementation\nit('should call repo.getConversation', ...)\n\n\u002F\u002F Correct — describes behavior\nit('should return cached task without hitting repo on second call', ...)\nit('should reject with error when conversation does not exist', ...)\n```\n\n**2. Every describe block must cover at least one failure path**\n\nHappy-path-only tests leave the most dangerous code untested.\n\n**3. One behavior per test**\n\nKeep each `it()` focused. More than 3 `expect()` calls in one test is a signal it is testing too much at once.\n\n**4. Self-check**\n\nAfter writing a test, mentally delete the core logic it targets. If the test would still pass, rewrite it — it is not guarding anything.\n\n**5. Start from risk, not from coverage gaps**\n\nList scenarios most likely to produce bugs. Write those first. Coverage is the outcome, not the starting point.\n\n### Step 3: Run Tests\n\n```bash\nbun run test              # Run all tests (REQUIRED before every commit)\nbun run test:coverage     # Check coverage (before opening a PR)\n```\n\n### Step 4: Verify Coverage\n\n**Coverage target**: ≥ 80% for all source files matched by `vitest.config.ts` → `coverage.include` (currently `src\u002F**\u002F*.{ts,tsx}` plus a few scripts).\n\nNew source files are automatically included in coverage — no manual config changes needed. If a new file is accidentally excluded by a rule in `coverage.exclude`, remove it from the exclude list.\n\n### Step 5: Update Existing Tests\n\nWhen modifying logic, check if existing tests need updating:\n\n```bash\nbun run test -- --reporter=verbose   # See which tests pass\u002Ffail with names\n```\n\nIf a test fails because the behavior changed intentionally, update the test. If it fails unexpectedly, investigate.\n\n## Edge Case Checklist\n\nWhen testing a module, verify:\n\n- [ ] `null` \u002F `undefined` inputs handled\n- [ ] Empty arrays\u002Fobjects handled\n- [ ] Error thrown by dependencies handled\n- [ ] Boundary values (0, -1, max, empty string)\n- [ ] Async operations (timeout, rejection, cancellation)\n\n## Quick Checklist\n\nBefore submitting code:\n\n- [ ] New features have corresponding test cases\n- [ ] Modified logic has updated tests\n- [ ] `bun run test` passes\n- [ ] Tests describe **behavior**, not implementation\n- [ ] At least one failure path per describe block\n- [ ] New source files are not accidentally excluded by `coverage.exclude`\n- [ ] `bun run test:coverage` meets ≥ 80% target\n\n## Common Mistakes\n\n| Mistake                           | Correct                                       |\n| --------------------------------- | --------------------------------------------- |\n| Testing implementation details    | Test observable behavior                      |\n| Only testing happy path           | Must include at least one failure path        |\n| 5+ expects in one `it()`          | Split into separate tests                     |\n| Skipping tests for \"simple\" code  | Simple code breaks too — test the risky parts |\n| Writing tests after saying \"done\" | Tests are part of \"done\", not an afterthought |\n",{"name":5,"description":7},"main","3c19e850e7cd377dc8b32ba3fea9becd16595524",".claude\u002Fskills\u002Ftesting",0,"https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision","https:\u002F\u002Fgithub.com\u002Ffinewood2008","Founder & CEO of Centaur AI · Humans lead, AI executes — the Centaur Loop is the smallest work unit for building AI employees.","2026-07-19 22:38:44",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add finewood2008\u002Fcentaurai-decision --skill testing",{"tool":38,"command":39},"bunx","bunx skills add finewood2008\u002Fcentaurai-decision --skill testing",{"tool":41,"command":42},"pnpm","pnpm dlx skills add finewood2008\u002Fcentaurai-decision --skill testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftesting\u002FSKILL.md",true,[],[47,53,59,66,73,80],{"skillNo":48,"name":49,"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":50,"categories":51,"keywords":52,"publishedAt":19},"01M77RBY5HGGVSV6XACWRA1NQK","aionui-troubleshooting","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002Fresources\u002Fbutler\u002Fskills\u002Faionui-troubleshooting\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"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":56,"categories":57,"keywords":58,"publishedAt":19},"01M77RBV90N96AHP1KXQGRSS2M","aionui-config","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002Fresources\u002Fbutler\u002Fskills\u002Faionui-config\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M77RBKVHZZXCCY96ERY1QC1R","pr-verify","PR Verification & Merge: verify bot:ready-to-merge PRs with impact analysis, test supplementation, and one-click merge.\nUse when: (1) User says \"\u002Fpr-verify\", (2) User wants to verify and merge ready PRs.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpr-verify\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M77RBF897GD44DVE4GJTXY82","pr-ship","End-to-end PR lifecycle: create PR, wait for CI, review, fix issues, merge — all in one invocation.\nUse when: (1) User says \"\u002Fpr-ship\", (2) User wants to ship current changes as a complete PR lifecycle,\n(3) User wants to resume shepherding an existing PR.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpr-ship\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"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},"01M77RBA6V98VM087EZJYWZRD1","pr-review","PR Code Review (Local): perform a thorough local code review with full project context.\nUse when: (1) User asks to review a PR, (2) User says \"\u002Fpr-review\", (3) User wants to review code changes before merging.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpr-review\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},"01M77RB5KHE6GYW77KPGKCQR8J","pr-fix","PR Review Fix: automatically fix all issues identified in a pr-review report.\nUse when: (1) User says \"fix all review issues\", (2) User says \"\u002Fpr-fix\",\n(3) After pr-review skill has produced a report, (4) User wants to address PR review feedback.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-decision\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpr-fix\u002FSKILL.md",[],[]]