verify

Run verification commands and review output before asserting completion.

1|Updated Oct 3, 2023

Search Tags:#testing #quality assurance #verification #evidence #process #claims

Ready to run

npx skills add https://github.com/mt-krainski/twinkletaps --skill verify-mt-krainski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/mt-krainski/twinkletaps/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/mt-krainski/twinkletaps --skill verify-mt-krainski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents making unverified claims by enforcing a strict process of running commands and checking their output before asserting a status. It combats stale results and assumptions.

Core Features & Use Cases

Mandatory Verification: Ensures that any claim of success (e.g., tests passing, build succeeding, bug fixed) is preceded by running the relevant command and examining its output.
Evidence-Based Assertions: Promotes a culture of "evidence before assertions," requiring concrete proof for all status updates.
Use Case: Before declaring a feature complete and ready for merge, this Skill ensures you've run the test suite and confirmed zero failures, rather than assuming it works based on code changes alone.

Quick Start

Always run the verification command before claiming completion.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I verify test results before claiming a build is complete?▼

Evidence-based verification requires running the specific test or build commands and examining their output before reporting success. This process prevents stale assumptions and ensures every status claim is backed by concrete proof of passing tests or successful builds.

What is evidence-based verification in software development?▼

Evidence-based verification is a process that mandates running commands and checking their output before asserting a development status. It combats stale results by requiring concrete proof, ensuring claims like bug fixes or passing tests are backed by actual command execution.

How do I enforce mandatory verification of passing tests in my workflow?▼

You enforce mandatory verification by adopting a workflow that requires running commands and reviewing their output before declaring any task complete. This ensures claims of success, like passing tests or fixed bugs, are preceded by concrete command execution evidence.

Why do I need to run commands before asserting a bug is fixed?▼

You need to run commands before asserting a bug is fixed to maintain development workflow integrity and prevent unverified claims. Examining actual command output provides concrete evidence that the fix works, combating stale results and unfounded assumptions.

Does evidence-based verification work for general quality assurance claims?▼

Yes, evidence-based verification works for general quality assurance claims by enforcing a strict process of running commands and checking their output. It ensures any assertion of success, including passing tests or bug fixes, is backed by concrete proof.