verification-before-completion

Require executed verification commands before claiming task completion.

10|2|Updated Mar 10, 2026

Search Tags:#code quality #testing #verification #completion #evidence #assertions

Ready to run

npx skills add https://github.com/bugrabilge/bilge-development-kit --skill verification-before-completion-bugrabilge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/bugrabilge/bilge-development-kit/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/bugrabilge/bilge-development-kit --skill verification-before-completion-bugrabilge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of task completion, bug fixes, or successful test runs by enforcing a strict verification process before any assertion of success is made.

Core Features & Use Cases

Mandatory Verification: Ensures that all claims of completion, passing tests, or bug fixes are backed by fresh, executed verification commands and their output.
Prevents False Positives: Stops the AI from reporting success based on assumptions, past runs, or incomplete checks.
Use Case: Before committing code or creating a Pull Request, the AI must run the test suite, verify the build command exits with code 0, and confirm that the specific bug fix addresses the reported issue with evidence, before stating "Task complete" or "Bug fixed".

Quick Start

Always run the verification command and check its output before claiming any 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 prevent false claims of task completion before creating a pull request?▼

To prevent false claims of task completion before a pull request, enforce an evidence-before-assertions policy requiring fresh command execution and output verification for all success claims. This ensures build and test validations are independently executed rather than assumed.

Why does the AI report bug fixes are complete without running the test suite?▼

AI reports bug fixes as complete without running tests due to premature assertions based on assumptions. Enforcing mandatory verification requires independent execution of test suites and checking exit code 0 to confirm the specific fix addresses the reported issue with evidence.

What is mandatory verification for code quality and task status reporting?▼

Mandatory verification for code quality is a strict policy requiring executed verification commands and their output before claiming any task, test run, or build is successful. It prevents false positives by stopping status reporting based on past runs or incomplete checks.

How to verify a successful build before committing code?▼

To verify a successful build before committing code, execute the build command independently and confirm it exits with code 0. This strict verification process ensures all claims of passing tests or requirement fulfillment are backed by fresh execution evidence.

Can I use automated verification to stop false positives in test runs?▼

Yes, you can use automated verification to stop false positives in test runs by enforcing a policy that requires independent command execution and output validation. This prevents the AI from reporting success based on assumptions or incomplete checks before stating a task is complete.

When should I not use evidence-based verification for completion claims?▼

Evidence-based verification for completion claims should not be skipped when committing code, fixing bugs, or creating pull requests. There are no safe exceptions to bypassing execution checks, as assuming success without fresh output risks integrating false positives and unresolved issues.