verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: sheer-rey

Require fresh command output before marking tasks complete.

Updated Sep 27, 2024

Search Tags:#testing #validation #verification #quality #evidence #builds

Ready to run

npx skills add https://github.com/sheer-rey/PowerBash --skill verification-before-completion-sheer-rey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/sheer-rey/PowerBash/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/sheer-rey/PowerBash --skill verification-before-completion-sheer-rey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false completion claims by enforcing fresh verification evidence before you say work is finished, tested, fixed, or ready to ship.

Core Features & Use Cases

Evidence-first validation: Requires running the relevant command and reading its output before making success claims.
Testing and build checks: Helps confirm unit tests, linting, builds, and regression tests with actual results instead of assumptions.
Pre-commit and PR safety: Useful when preparing a commit, opening a pull request, or handing work off to another agent and you need proof that it is correct.

Quick Start

Ask the skill to verify the work by running the exact validation command and reporting only evidence-backed results.

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 completion claims when marking a bug fix or pull request as done?▼

To prevent false completion claims, you must require fresh verification evidence before marking work done. This involves running full validation commands, checking their exit status and failure counts, and reporting only evidence-backed results to prove completion.

What is evidence-first validation for software builds and testing?▼

Evidence-first validation is the process of running a relevant command and reading its actual output before claiming success. It ensures that testing, builds, and regression checks are confirmed with real command results rather than assumptions.

How do I verify test results and check exit status before committing code?▼

You verify test results by executing the exact validation commands and analyzing the output. This process enforces checking the exit status and counting any failures, ensuring you only report success when backed by fresh command evidence.

Does this verification approach work for pre-commit checks and unit tests?▼

Yes, this verification approach works for pre-commit checks and unit tests. It is designed to confirm linting, builds, and regression tests with actual results, making it useful when preparing a commit, opening a pull request, or handing work off.

What is the best way to prove a build or task is actually finished before claiming it?▼

The best way to prove a build is finished is to enforce fresh verification evidence before making success claims. You must run full validation commands, check for failure counts, and demonstrate success strictly through actual command output.

When do I need to run validation commands instead of assuming my code changes are ready?▼

You need to run validation commands whenever a task's success must be demonstrated, such as after bug fixes, unit tests, or pull request preparations. It prevents false completion claims by requiring actual command output evidence before marking work done.