Unit test
Project-aware unit testing guide with mock patterns, TDD discipline, and best practices. Auto-detects test framework (Jest/Vitest) and provides appropriate examples. Use when: (1) writing or fixing unit tests, (2) user says "寫測試", "write test", "補測試", "add test", (3) user encounters mock patterns or test failures, (4) user asks how to test a composable, component, or store, (5) user says "mock imports", "test store", "怎麼測", "測試怎麼寫", (6) reviewing test quality: "unit test review", "review tests", "check test quality", "測試審查", "review 測試", "測試品質", "檢查測試品質", (7) TDD workflow: "TDD", "test driven", "紅綠燈", "先寫測試", "test first", "red green refactor".From its SKILL.md
npx -y skills add HsuanYuLee/polaris --skill unit-testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 1 command, including `Execute post-task-reflection-checkpoint.md before reporting completion.`.
SKILL.md
2.8 KB, 549 tokens by cl100k_base, as published. Nobody here has run it
Unit Test
unit-test 是 project-aware unit testing guide,用於寫測試、修測試、review test quality,
或在 engineering 中執行 TDD。
Contract
測試要驗證真實行為,不用 mock-only assertions 製造假綠燈。明確 TDD 時採 red / green / refactor;一般補測試時仍要先確認現有 framework、local patterns、test command。
Reference Loading
| Situation | Load |
|---|---|
| Any run | unit-test-detection-tdd-flow.md, tdd-smart-judgment.md |
| Jest / Vitest / Vue examples | unit-test-framework-patterns.md |
| Coverage / test quality review | unit-test-strategy-coverage.md |
| Delegated test work | sub-agent-roles.md Completion Envelope |
Flow
- Detect test framework and repo-specific test command.
- Locate existing tests near the target module and copy local style.
- Decide whether strict TDD applies using
tdd-smart-judgment.md. - Plan test cases from simplest to most complex.
- In TDD mode, run one red/green/refactor cycle per case.
- In non-strict mode, write focused tests alongside implementation.
- 先跑 narrow test command,再跑 owning workflow 要求的 broader command。
- Report changed tests, command results, coverage gaps, and any intentional non-testable scope.
Hard Rules
- 不可為了 pass 而弱化 assertions、加入
.skip()、刪 tests、或加 type suppressions。 - Public behavior 可測時,不測 private implementation details。
- 不 inline 大量 mock data;改用 fixtures 或 factories。
- 除非 dependency boundary 需要,不用 mock 取代 real source logic。
- 每個 test 驗證一個 behavior;需要用 "and" 命名時通常應拆開。
- Delegated test work must return the Completion Envelope.
Completion
回傳 framework、commands run、TDD 時的 red/green evidence、files changed、remaining coverage risk,以及 skipped test rationale。
Post-Task Reflection (required)
Execute post-task-reflection-checkpoint.md before reporting completion.
What ships with it: 11 files
81.6 KB alongside SKILL.md, 7 of them executable
references/
scripts/
- ci-contract-discover.shruns624 B
- ci-local-env-classify.pyruns8.7 KB
- ci-local-generate.shruns2.8 KB
- lib/ci_ci_contract_discover_1.pyruns18.2 KB
- lib/ci_ci_local_generate_1.pyruns39.5 KB
- lib/ci-local-path.shruns2.6 KB
- lib/main-checkout.shruns1.6 KB