verification-before-completion

Run verification commands and analyze output before claiming task completion.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Luizfbm/Dev-roast --skill verification-before-completion-luizfbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Luizfbm/Dev-roast/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/Luizfbm/Dev-roast --skill verification-before-completion-luizfbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of prematurely claiming work is finished without actual evidence, ensuring that all assertions of success are backed by verifiable output.

Core Features & Use Cases

  • Evidence-Based Validation: Mandates the execution of specific commands to prove that tests pass, builds succeed, or bugs are fixed before any completion claim is made.
  • Rationalization Prevention: Provides a structured framework to identify and stop common excuses for skipping verification, such as relying on assumptions or partial checks.
  • Use Case: Before submitting a pull request or marking a task as done, use this skill to systematically run the required test suites and build commands to confirm the code is truly ready.

Quick Start

Apply the verification before completion protocol to your current task by running the necessary test and build commands to confirm the state of the codebase before reporting success.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I enforce verification before claiming task completion in software development workflows?

Enforce verification before task completion by mandating the execution of full test suites and build commands to objectively analyze output before any success status is asserted.

What's the best way to prevent premature completion claims during pull request submissions?

Prevent premature completion claims during pull request submissions by applying a strict verification protocol that requires running specific commands and proving tests pass before reporting readiness.

How does evidence-based validation work for code review and quality assurance?

Evidence-based validation works by requiring the execution of specific verification commands to prove builds succeed or bugs are fixed, ensuring all success assertions are backed by verifiable output.

Can I use this verification protocol for agent-based task delegation?

Yes, you can use this verification protocol for agent-based task delegation to ensure technical accuracy by requiring agents to execute verification commands and analyze objective output before asserting task completion.

How to stop rationalization and assumptions when skipping code review verification?

Stop rationalization when skipping code review verification by applying a structured framework that identifies common excuses and mandates full verification command execution instead of relying on partial checks or assumptions.

Why does marking a task as done fail without running quality assurance tests?

Marking a task as done fails without running quality assurance tests because premature claims lack verifiable output, meaning success assertions are based on assumptions rather than objective evidence from test execution.