mcpField
V
verification-and-testing

verification-and-testing

github.com/alexbrunoOther09 installsUpdated today
Repository

About verification-and-testing

verification-and-testing is a skill that requires fresh evidence before reporting work as complete or checks as passing. It helps coding agents map requirements to checks, write behavior-focused tests, and verify changes after the final edit.

Key features

  1. 01Require evidence before completion claims
  2. 02Map criteria to concrete checks
  3. 03Test behavior and edge cases
  4. 04Run checks after final edits
  5. 05Report verification scope

Use cases

  1. 01Verify a change against acceptance criteria
  2. 02Test edge cases and error paths
  3. 03Confirm checks after the final edit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/alexbruno/dev-skills --skill verification-and-testing

After installing, type/verification-and-testingin Claude Code to confirm it loaded.

Details

From the project README

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.md and the verification strategy in workflow/PLAN.md to 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:

  1. Run the relevant unit/integration tests, linter, typechecker, and build commands.
  2. Confirm all executed checks pass with zero skipped or relaxed assertions.
  3. Report the exact scope of what was run (e.g., full suite vs. targeted subset, any environment limitations).

Comments

Markdown supported