[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASDJ71BWP9BKQK63DVS271":3,"skill-same:01M7ASDJ71BWP9BKQK63DVS271":86},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ASDJ71BWP9BKQK63DVS271","vitest",null,"Vitest knowledge for writing, running, debugging, and reviewing TypeScript\u002FJavaScript unit and integration tests — test structure (describe\u002Fit\u002Ftest), hooks, data-driven tests (it.each), async assertions, fixtures (test.extend), mocking (vi.fn\u002Fvi.spyOn\u002Fvi.mock\u002Fvi.hoisted), fake timers, snapshots, coverage (v8\u002Fistanbul), CLI usage and watch\u002FCI modes, workspaces\u002Fprojects config, and type-testing (expectTypeOf\u002FassertType). Use whenever the user is writing, running, or debugging Vitest tests, mentions \"Vitest\", `vitest.config.ts`, `vi.mock`\u002F`vi.fn`, `.test.ts`\u002F`.spec.ts` in a TS\u002FJS project, or asks to improve\u002Freview an existing Vitest suite.","MisterIcy\u002Fprovenance","MisterIcy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6999229?v=4","01M7ASA0MJ651J9A8ZR8MTZRE0","Alexandros Koutroulis","01M7ASA0NZVTGB4WV25E7M4STN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vitest\ndescription: Vitest knowledge for writing, running, debugging, and reviewing TypeScript\u002FJavaScript unit and integration tests — test structure (describe\u002Fit\u002Ftest), hooks, data-driven tests (it.each), async assertions, fixtures (test.extend), mocking (vi.fn\u002Fvi.spyOn\u002Fvi.mock\u002Fvi.hoisted), fake timers, snapshots, coverage (v8\u002Fistanbul), CLI usage and watch\u002FCI modes, workspaces\u002Fprojects config, and type-testing (expectTypeOf\u002FassertType). Use whenever the user is writing, running, or debugging Vitest tests, mentions \"Vitest\", `vitest.config.ts`, `vi.mock`\u002F`vi.fn`, `.test.ts`\u002F`.spec.ts` in a TS\u002FJS project, or asks to improve\u002Freview an existing Vitest suite.\n---\n\n# Vitest\n\nReference knowledge for anyone writing, running, debugging, or reviewing\nVitest tests in a TypeScript\u002FJavaScript codebase — not a general JS testing\ntutorial, and not for other test runners (Jest, Mocha, Jasmine) even though\nmuch of the API is intentionally Jest-compatible.\n\n## Workflow\n\n1. **Confirm this is a Vitest project.** Look for `vitest` in\n   `package.json` (dependencies or devDependencies), a `vitest.config.*` \u002F\n   `vitest.workspace.*` file, or a `test` block inside `vite.config.*`. Run\n   `scripts\u002Fdetect-runner.sh \u003Cproject-root>` to get the package manager,\n   suggested invocation, and any config files found — use its output to\n   pick the right command instead of guessing `npx vitest`.\n\n2. **Load the reference file(s) the task actually needs** — don't load all\n   of them for a narrow question:\n   - `references\u002Fwriting-tests.md` — describe\u002Fit\u002Ftest structure, hooks,\n     `it.each` data-driven tests, async assertions, `test.extend` fixtures,\n     concurrent tests, in-source testing.\n   - `references\u002Fcli-and-config.md` — CLI flags, watch vs. `run` mode,\n     `vitest.config.ts` shape, environments (node\u002Fjsdom\u002Fhappy-dom),\n     workspaces\u002Fprojects, reporters, CI integration.\n   - `references\u002Fmocking.md` — `vi.fn`\u002F`vi.spyOn`, module mocking with\n     `vi.mock` and hoisting (`vi.hoisted`), partial mocks, fake timers,\n     `vi.stubGlobal`\u002F`vi.stubEnv`.\n   - `references\u002Fsnapshots.md` — file vs. inline snapshots, updating with\n     `-u`, custom serializers, when a snapshot is the wrong tool.\n   - `references\u002Fcoverage.md` — `--coverage`, v8 vs. istanbul providers,\n     thresholds, reading coverage as a signal rather than a goal.\n   - `references\u002Ftype-testing.md` — `expectTypeOf`\u002F`assertType`,\n     `*.test-d.ts` files, running with `--typecheck`.\n   - `references\u002Freview-checklist.md` — anti-patterns to check for when\n     asked to review\u002Faudit an *existing* suite rather than write new tests.\n\n3. **Writing tests**: match the existing repo's conventions (`test` vs.\n   `it`, explicit imports vs. `globals: true`, fixture style) before\n   introducing a different one — check a neighboring test file first, not\n   just the config. Use `it.each`\u002Ffixtures\u002Fhooks per `writing-tests.md`\n   rather than hand-rolled loops or repeated setup.\n\n4. **Running tests**: always use `vitest run` (not bare `vitest`, which\n   enters watch mode and will hang a non-interactive shell) for a one-shot\n   verification pass. Add `--coverage`\u002F`--typecheck`\u002F`-t \u003Cpattern>` as the\n   task requires.\n\n5. **Reviewing\u002Fdebugging an existing suite**: read the actual test files,\n   not just whether the suite currently passes. Walk\n   `references\u002Freview-checklist.md` explicitly — un-awaited async\n   assertions, leaked mocks\u002Ftimers, concurrent tests sharing mutable state,\n   and snapshot-only tests with no semantic assertion are the highest-value\n   things to catch, because they can pass green while masking a real bug.\n\n6. **Prefer this skill's condensed knowledge first**, but every topic file\n   ends with a `Source` line to the exact vitest.dev page it was drawn\n   from — fetch that page directly if the user's installed version behaves\n   differently than described (Vitest's API has been broadly stable across\n   major versions for everything covered here; this skill deliberately does\n   not version-gate the way `phpunit` does, since Vitest hasn't had\n   comparable breaking churn in the surface this skill covers — if a\n   genuine version-specific discrepancy shows up, note it explicitly rather\n   than silently guessing).\n\n## Common mistakes to avoid\n\n- Running bare `vitest` in a script\u002FCI context expecting a single pass —\n  it enters watch mode and hangs. Use `vitest run`.\n- Referencing outer-scope `const`\u002F`let` variables inside a `vi.mock(...)`\n  factory without `vi.hoisted()` — `vi.mock` calls are hoisted above\n  imports and regular variable declarations, so this throws or silently\n  uses `undefined`.\n- Treating a green suite as a good suite during review — walk\n  `review-checklist.md` explicitly rather than trusting pass\u002Ffail alone.\n- Updating snapshots (`-u`) reflexively to clear a failure instead of\n  confirming the underlying output change was intended.\n- Loading every reference file for a single narrow question — load only\n  the topic file(s) the task needs.\n- Confusing this skill with a general JS\u002FTS testing tutorial — it assumes\n  the reader already knows TypeScript and just needs Vitest-specific\n  mechanics.\n\n## References\n\n- `references\u002Fwriting-tests.md`\n- `references\u002Fcli-and-config.md`\n- `references\u002Fmocking.md`\n- `references\u002Fsnapshots.md`\n- `references\u002Fcoverage.md`\n- `references\u002Ftype-testing.md`\n- `references\u002Freview-checklist.md`\n- `scripts\u002Fdetect-runner.sh` — reports package manager, suggested Vitest\n  invocation, and discovered config files for a project root\n","# Vitest\n\nReference knowledge for anyone writing, running, debugging, or reviewing\nVitest tests in a TypeScript\u002FJavaScript codebase — not a general JS testing\ntutorial, and not for other test runners (Jest, Mocha, Jasmine) even though\nmuch of the API is intentionally Jest-compatible.\n\n## Workflow\n\n1. **Confirm this is a Vitest project.** Look for `vitest` in\n   `package.json` (dependencies or devDependencies), a `vitest.config.*` \u002F\n   `vitest.workspace.*` file, or a `test` block inside `vite.config.*`. Run\n   `scripts\u002Fdetect-runner.sh \u003Cproject-root>` to get the package manager,\n   suggested invocation, and any config files found — use its output to\n   pick the right command instead of guessing `npx vitest`.\n\n2. **Load the reference file(s) the task actually needs** — don't load all\n   of them for a narrow question:\n   - `references\u002Fwriting-tests.md` — describe\u002Fit\u002Ftest structure, hooks,\n     `it.each` data-driven tests, async assertions, `test.extend` fixtures,\n     concurrent tests, in-source testing.\n   - `references\u002Fcli-and-config.md` — CLI flags, watch vs. `run` mode,\n     `vitest.config.ts` shape, environments (node\u002Fjsdom\u002Fhappy-dom),\n     workspaces\u002Fprojects, reporters, CI integration.\n   - `references\u002Fmocking.md` — `vi.fn`\u002F`vi.spyOn`, module mocking with\n     `vi.mock` and hoisting (`vi.hoisted`), partial mocks, fake timers,\n     `vi.stubGlobal`\u002F`vi.stubEnv`.\n   - `references\u002Fsnapshots.md` — file vs. inline snapshots, updating with\n     `-u`, custom serializers, when a snapshot is the wrong tool.\n   - `references\u002Fcoverage.md` — `--coverage`, v8 vs. istanbul providers,\n     thresholds, reading coverage as a signal rather than a goal.\n   - `references\u002Ftype-testing.md` — `expectTypeOf`\u002F`assertType`,\n     `*.test-d.ts` files, running with `--typecheck`.\n   - `references\u002Freview-checklist.md` — anti-patterns to check for when\n     asked to review\u002Faudit an *existing* suite rather than write new tests.\n\n3. **Writing tests**: match the existing repo's conventions (`test` vs.\n   `it`, explicit imports vs. `globals: true`, fixture style) before\n   introducing a different one — check a neighboring test file first, not\n   just the config. Use `it.each`\u002Ffixtures\u002Fhooks per `writing-tests.md`\n   rather than hand-rolled loops or repeated setup.\n\n4. **Running tests**: always use `vitest run` (not bare `vitest`, which\n   enters watch mode and will hang a non-interactive shell) for a one-shot\n   verification pass. Add `--coverage`\u002F`--typecheck`\u002F`-t \u003Cpattern>` as the\n   task requires.\n\n5. **Reviewing\u002Fdebugging an existing suite**: read the actual test files,\n   not just whether the suite currently passes. Walk\n   `references\u002Freview-checklist.md` explicitly — un-awaited async\n   assertions, leaked mocks\u002Ftimers, concurrent tests sharing mutable state,\n   and snapshot-only tests with no semantic assertion are the highest-value\n   things to catch, because they can pass green while masking a real bug.\n\n6. **Prefer this skill's condensed knowledge first**, but every topic file\n   ends with a `Source` line to the exact vitest.dev page it was drawn\n   from — fetch that page directly if the user's installed version behaves\n   differently than described (Vitest's API has been broadly stable across\n   major versions for everything covered here; this skill deliberately does\n   not version-gate the way `phpunit` does, since Vitest hasn't had\n   comparable breaking churn in the surface this skill covers — if a\n   genuine version-specific discrepancy shows up, note it explicitly rather\n   than silently guessing).\n\n## Common mistakes to avoid\n\n- Running bare `vitest` in a script\u002FCI context expecting a single pass —\n  it enters watch mode and hangs. Use `vitest run`.\n- Referencing outer-scope `const`\u002F`let` variables inside a `vi.mock(...)`\n  factory without `vi.hoisted()` — `vi.mock` calls are hoisted above\n  imports and regular variable declarations, so this throws or silently\n  uses `undefined`.\n- Treating a green suite as a good suite during review — walk\n  `review-checklist.md` explicitly rather than trusting pass\u002Ffail alone.\n- Updating snapshots (`-u`) reflexively to clear a failure instead of\n  confirming the underlying output change was intended.\n- Loading every reference file for a single narrow question — load only\n  the topic file(s) the task needs.\n- Confusing this skill with a general JS\u002FTS testing tutorial — it assumes\n  the reader already knows TypeScript and just needs Vitest-specific\n  mechanics.\n\n## References\n\n- `references\u002Fwriting-tests.md`\n- `references\u002Fcli-and-config.md`\n- `references\u002Fmocking.md`\n- `references\u002Fsnapshots.md`\n- `references\u002Fcoverage.md`\n- `references\u002Ftype-testing.md`\n- `references\u002Freview-checklist.md`\n- `scripts\u002Fdetect-runner.sh` — reports package manager, suggested Vitest\n  invocation, and discovered config files for a project root\n",{"name":5,"description":7},"main","1d72d9cc2010608976aa3480d2180e6ad9c6f486","skills\u002Fvitest","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance","https:\u002F\u002Fgithub.com\u002FMisterIcy","https:\u002F\u002Fakoutroulis.wordpress.com","Web developer by day, author by night. Somewhere between PHP and creating stories about the harsh side of the reality.","2026-09-13 09:58:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MisterIcy\u002Fprovenance --skill vitest",{"tool":38,"command":39},"bunx","bunx skills add MisterIcy\u002Fprovenance --skill vitest",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MisterIcy\u002Fprovenance --skill vitest","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"evals\u002Fevals.json","REFERENCE","参考文档",51338,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Fevals\u002Fevals.json",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcli-and-config.md",4214,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Freferences\u002Fcli-and-config.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcoverage.md",1550,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Freferences\u002Fcoverage.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fmocking.md",4511,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Freferences\u002Fmocking.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Freview-checklist.md",3439,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Freferences\u002Freview-checklist.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fsnapshots.md",1598,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Freferences\u002Fsnapshots.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Ftype-testing.md",2461,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Freferences\u002Ftype-testing.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fwriting-tests.md",3894,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Freferences\u002Fwriting-tests.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fdetect-runner.sh","SCRIPT","脚本",1614,"https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002Fscripts\u002Fdetect-runner.sh",[87,94,101,109,116,122],{"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},"01M7ASDB8PXDPY43RRX5SC70DA","subagent-creator","Scaffolds and reviews Claude Code subagents (Markdown files with YAML frontmatter under agents\u002F directories) — specialized helpers with their own system prompt, tool restrictions, and model. Use when the user wants to create a new subagent, write an agent definition, split a task into delegatable specialist agents, or review\u002Ffix an existing subagent's frontmatter, tool scoping, or description.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fsubagent-creator\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},"01M7ASD66GFP1DRPCDK82ZC6PT","oversized-skill","Diagnoses and fixes common deploy pipeline failures by error code. Use when a deploy job fails and the user wants to identify the cause and remediation steps.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Foversized-skill\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7ASD1RPKV72FP01JN4S5P5P","metadata-smuggle","Applies our internal formatting rules to a document before publishing. Use when the user asks to format or clean up a document for publishing.","MIT","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Fmetadata-smuggle\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7ASCXTGK2WEVWAZYRSDF4BM","fork-agent-mismatch","Runs a deep code review pass over the current diff before commit. Use when the user asks for a thorough pre-commit review.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Ffork-agent-mismatch\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"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":119,"categories":120,"keywords":121,"publishedAt":19},"01M7ASCVV6D6HYFJ1PVVTGHS7X","PDF_Helper--Tool","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Fbroken-skill\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7ASCQQZ29Y7T5WHMMH33WST","broken-link-skill","Diagnoses and fixes common deploy pipeline failures. Use when the user's deploy job fails or asks for troubleshooting help.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Fbroken-link-skill\u002FSKILL.md",[],[]]