skills.rest
ftzi
ftziCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Verify task completion by running commands and analyzing output before claiming success.

7|Updated Dec 7, 2025
Search Tags:#code quality#testing#CI/CD#verification#assurance#task completion
One-click install
npx skills add https://github.com/ftzi/livespec --skill verification-before-completion-ftzi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ftzi/livespec/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/ftzi/livespec --skill verification-before-completion-ftzi

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 is made. It combats the inefficiency and trust erosion caused by unverified progress.

Core Features & Use Cases

  • Mandatory Verification: Ensures that all claims of success (tests passing, bugs fixed, builds succeeding, work complete) are backed by fresh, executed verification commands and their output.
  • Red Flag Identification: Helps users recognize and avoid common rationalizations for skipping verification.
  • Use Case: Before committing code or creating a Pull Request, an AI agent must run the defined test suite and confirm zero failures in the output, then present this evidence before stating the tests have passed.

Quick Start

Always run the verification command and confirm its output before claiming any work is complete or successful.

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 code completion in CI/CD?▼

To enforce verification before claiming code completion, you must execute specific test or build commands and analyze their output to confirm zero failures before communicating any success assertions.

What are common red flags for skipping testing verification during development?▼

Common red flags for skipping testing verification include rationalizing that changes are too small to test or assuming previous builds guarantee current success, which erodes trust and causes premature task completion claims.

How to verify bug fixes before creating a pull request?▼

To verify bug fixes before creating a pull request, run the defined test suite, confirm zero failures in the command output, and present this evidence before stating the bug has been successfully fixed.

Does evidence before claims protocol apply to all stages of software development?▼

Yes, the evidence before claims protocol applies to all stages of software development, requiring fresh verification command output to confirm test runs, bug fixes, and build successes before making any assertions.

Why does claiming task completion without running build commands cause inefficiency?▼

Claiming task completion without running build commands causes inefficiency and trust erosion because unverified progress introduces hidden failures into the pipeline that require later debugging and rework.

Related Skills

Explore More Software Engineering Skills→
pur3v4d3rpur3v4d3r
6

verification-before-completion

Run verification and attach fresh output before claiming completion.

Community
Advanced
kk20300113-pngkk20300113-png

land-and-deploy

Merge pull requests and verify production health via canary checks.

Community
Advanced
cxnaivecxnaive

requesting-code-review

Automate pre-commit code verification with static security analysis and regression checks.

Community
Advanced
HumanBean17HumanBean17
8

verification-before-completion

Execute validation commands and confirm output before marking tasks complete.

Community
Intermediate