verification-first

What problem does it solve?

This Skill eliminates speculative language and enforces an evidence-based approach to software development, ensuring that every claim about code behavior is backed by concrete test results. It reduces miscommunication and improves code reliability.

Core Features & Use Cases

• Banned Language Enforcement: Replaces vague terms like "should work" or "probably fixes" with explicit "VERIFIED" or "UNVERIFIED" statements, demanding proof for all claims.
• Structured Verification Evidence: Provides a clear, standardized format for documenting test results, including file paths, exact commands run, and relevant assertion output.
• Red Flag Detection: Identifies and flags common anti-patterns in communication that indicate a lack of verification, prompting developers to provide necessary evidence.
• Use Case: During a code review, a developer makes a claim about a bug fix. This skill can be used to prompt them to provide explicit verification evidence, including the test command and output, ensuring the fix is truly confirmed rather than assumed.

Quick Start

Review the pull request description and replace any instances of "this should fix the bug" with explicit verification evidence, including the test command and output.