How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/alexbruno/dev-skills --skill verification-and-testingBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
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).