skills.rest
Jackiexiao
JackiexiaoCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforce evidence-based verification before claiming work completion or passing statuses.

Updated Feb 20, 2026
Search Tags:#testing#quality assurance#code review#verification#completion#assertions
One-click install
npx skills add https://github.com/Jackiexiao/jackie-skills-dev --skill verification-before-completion-jackiexiao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Jackiexiao/jackie-skills-dev/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/Jackiexiao/jackie-skills-dev --skill verification-before-completion-jackiexiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of completion or success by enforcing a strict verification process before any assertion is made, ensuring accuracy and preventing costly rework.

Core Features & Use Cases

  • Mandatory Verification: Ensures that all claims of work completion, passing tests, or bug fixes are backed by fresh, executed verification commands and their output.
  • Reduces False Positives: Prevents shipping code with undetected errors by requiring explicit checks for tests, linters, and builds.
  • Use Case: Before committing code or creating a pull request, use this Skill to ensure all automated tests have passed and the linter reports no errors, preventing the introduction of regressions.

Quick Start

Always run the verification command and check its output before claiming any status or expressing satisfaction.

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 a verification step before claiming a bug fix is complete?▼

You can prevent premature completion claims by enforcing a strict evidence-first policy that requires executing verification commands and confirming their output before reporting any bug fix or passing status.

What is the best way to prevent false positives when running tests and linters before a pull request?▼

Preventing false positives requires mandatory execution of test, linter, and build commands with explicit output confirmation before committing code or creating pull requests, stopping regressions from being introduced.

Why do I need to verify code execution output before committing changes?▼

Verifying execution output before committing ensures accuracy and prevents costly rework by stopping premature success claims, requiring that all automated tests pass and linters report zero errors before any code is committed.

Does this evidence before assertions policy apply to all code review and quality assurance stages?▼

Yes, the evidence before assertions policy applies to all quality assurance and code review stages, acting as a strict gate function that must be satisfied before committing, creating pull requests, or reporting any successful work status.

How to set up a mandatory verification gate for status updates and pull requests?▼

Set up a mandatory verification gate by enforcing a strict policy that requires running verification commands and checking their output before allowing any status updates, pull requests, or completion claims to be processed.

Related Skills

Explore More Software Engineering Skills→
kage1020kage1020

check

Run tests, linting, and builds to verify code quality.

Community
Intermediate
johannesfritzjohannesfritz
1

run-test-suite

Run pytest or Playwright/vitest suites and report pass/fail results.

Community
Advanced
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate
qodex-aiqodex-ai
39

quality-validation

Run verification commands and present output before claiming task completion.

Official
Intermediate