verification-before-completion

Execute validation commands and confirm output before marking tasks complete.

8|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/HumanBean17/jrag --skill verification-before-completion-humanbean17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/HumanBean17/jrag/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/HumanBean17/jrag --skill verification-before-completion-humanbean17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common AI failure of claiming work is finished or correct without actually verifying the results, ensuring that all assertions are backed by concrete evidence.

Core Features & Use Cases

  • Verification Gatekeeping: Forces a mandatory check of commands, exit codes, and output before any success claim can be made.
  • Evidence-Based Reporting: Ensures that every status update is accompanied by the specific command output that proves the claim.
  • Use Case: When fixing a bug, this skill mandates that you run the failing test, verify it fails, apply the fix, run the test again, and confirm it passes before reporting the bug as resolved.

Quick Start

Run the verification command for the current task and confirm the output matches the expected success criteria before stating that the work is complete.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I stop AI from claiming code is finished without running tests?

To stop AI from claiming code is finished without running tests, enforce a verification protocol that requires fresh execution of validation commands and output integrity confirmation before any task completion assertions are made.

What is evidence-based task completion in software development?

Evidence-based task completion is a verification protocol requiring that all success claims are backed by concrete command output, ensuring code changes, test results, or system builds are proven valid through fresh execution before being marked as finished.

How do I verify bug fixes before reporting them as resolved?

To verify bug fixes before reporting them as resolved, run the failing test to confirm it fails, apply the fix, run the test again, and execute validation commands to confirm the output matches expected success criteria.

Can I enforce a verification gate for code changes without external dependencies?

Yes, you can enforce a verification gate for code changes without external dependencies by mandating a check of commands, exit codes, and output before any success claim can be made, ensuring all status updates are accompanied by command output.

Why does my AI agent report success without checking build results?

Your AI agent reports success without checking build results because it lacks a strict verification protocol enforcing mandatory fresh execution of validation commands and output integrity confirmation before making any success assertions.