使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/alexbruno/dev-skills --skill verification-and-testing开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Verification & Testing
Never claim a change works, passes, or is complete without fresh, direct verification evidence collected after the final edit.
Core Rule
Evidence before completion claims. If you did not run a check after your last change and observe its output, do not report it as passing.
1. Align Verification with workflow/SPEC.md
- Map every acceptance criterion in
workflow/SPEC.mdand the verification strategy inworkflow/PLAN.mdto a concrete check (automated test, build, lint, typecheck, or explicit runtime check). - Treat untested acceptance criteria as incomplete work.
2. Write Meaningful Tests
- Test behavior, not implementation details: Assert observable outputs, state transitions, and side effects so tests survive safe refactoring (
code-simplification). - Cover the edges: Include boundary values, empty/null inputs, invalid states, and error paths—not just the happy path.
- Keep tests isolated and deterministic: Avoid shared mutable state, real network calls, or time-dependent flakiness unless explicitly testing integration boundaries.
- Never weaken assertions: Do not relax, skip, or mock away the core behavior under test just to make a suite green.
3. Execution Gate After Final Edit
Before handing off work or moving to workflow/REVIEW.md:
- Run the relevant unit/integration tests, linter, typechecker, and build commands.
- Confirm all executed checks pass with zero skipped or relaxed assertions.
- Report the exact scope of what was run (e.g., full suite vs. targeted subset, any environment limitations).