verification

Name: verification
Availability: InStock
Author: Inteligentsensingsolutions

Run test, lint, and typecheck commands and record their outputs.

1|Updated Apr 13, 2026

Search Tags:#testing #linting #verification #e2e-testing #evidence-based #acceptance-criteria #typechecking

Ready to run

npx skills add https://github.com/Inteligentsensingsolutions/tdd-dev-workflow --skill verification-inteligentsensingsolutions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/Inteligentsensingsolutions/tdd-dev-workflow/tree/main/skills/verification
Command: npx skills add https://github.com/Inteligentsensingsolutions/tdd-dev-workflow --skill verification-inteligentsensingsolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unverified completion claims by enforcing that tests, linters, and typechecks are executed and their fresh outputs are inspected and recorded before saying work is done.

Core Features & Use Cases

Evidence-first Verification: Mandates running the actual verification commands and pasting the real output instead of relying on memory or assumptions.
Multi-step Checklist: Covers unit tests, linter results, type checking, and end-to-end tests where applicable, and maps acceptance criteria to concrete passing tests.
Clear Reporting Format: Requires structured reporting of successes and failures so partial success is transparent and traceable.
Use case: Before creating a pull request or marking an issue complete, run the verification checklist and include the exact outputs to support the completion claim.

Quick Start

Run the project's test, lint, and typecheck commands, paste their full outputs, and confirm each acceptance criterion is mapped to a passing test.

Frequently Asked Questions about verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce evidence-based verification before marking a code change done?▼

Evidence-based verification mandates running the project's actual test, lint, and typecheck commands, then pasting their fresh outputs to prove code changes are valid before claiming completion.

What is the best way to map acceptance criteria to passing tests in a pull request?▼

Mapping acceptance criteria to passing tests involves executing your test suite and explicitly linking each acceptance criterion to a concrete, freshly verified passing test output in your completion report.

How do I verify end-to-end tests and typechecks before completing an issue?▼

Verifying end-to-end tests and typechecks involves running the project's configured commands, collecting their outputs, and ensuring a multi-step checklist covers unit tests, linter results, type checking, and e2e tests.

Does this verification process work with any testing framework or linting tool?▼

This verification process works with any testing, linting, or typechecking tool because it requires running the project's specifically configured commands and collecting the outputs, rather than relying on built-in tools.

Why should I require fresh test outputs instead of relying on previous verification results?▼

Requiring fresh test outputs prevents unverified completion claims by ensuring that tests, linters, and typechecks are executed against the current codebase state, making partial success transparent and traceable.