skills.rest
diegocondo10
diegocondo10COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Verify completion claims by running full commands and inspecting outputs.

Updated Aug 23, 2026
Search Tags:#testing#quality assurance#verification#evidence#pre-commit#build validation
One-click install
npx skills add https://github.com/diegocondo10/sinai-intranet-backend --skill verification-before-completion-diegocondo10
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/diegocondo10/sinai-intranet-backend/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/diegocondo10/sinai-intranet-backend --skill verification-before-completion-diegocondo10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false completion claims by requiring fresh verification evidence before you say a task is done, fixed, or passing.

Core Features & Use Cases

  • Evidence-first workflow: Forces you to identify, run, and inspect the command that actually proves success.
  • Build and test validation: Useful before reporting that tests pass, a build succeeds, a bug is fixed, or a regression is resolved.
  • Commit and PR safety: Helps avoid shipping unverified work by checking results before creating commits, pull requests, or status updates.

Quick Start

Use this skill to verify your latest change by running the full relevant check and only then reporting the actual result.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I verify test results before claiming a code fix is complete?▼

Build validation requires running the full verification command, reading the complete output and exit code, and confirming there are no failures before stating success. This process ensures you have fresh evidence proving the build succeeds before reporting it.

What is the best way to prevent false completion claims in pre-commit checks?▼

Quality assurance verification works by requiring you to identify, run, and inspect the command that actually proves success before reporting a task as finished. This evidence-first workflow forces you to validate test results, builds, and code fixes against fresh output.

Do I need to run the full test suite to confirm a bug is fixed?▼

Yes, you need to run the full verification command and inspect the complete output and exit code to confirm a bug is fixed. Stating success requires fresh evidence that there are no failures in the actual test results or build validation output.

Can I use pre-PR status checks to avoid shipping unverified work?▼

Yes, you can use pre-PR status checks to avoid shipping unverified work by running the full relevant check and only then reporting the actual result. This ensures you check results and confirm there are no failures before creating commits or pull requests.

Related Skills

Explore More Software Engineering Skills→
xxihxxih
1

quality-verify

Run verification commands and record results in .quality/quality-check.md.

Community
Intermediate
zinohomezinohome

verification-before-completion

Require verification evidence before reporting software work as complete.

Community
Intermediate
sachio222sachio222

verification-before-completion

Require fresh verification evidence before claiming completion in pre-commit, pre-PR, and release workflows.

Community
Advanced
rishikanthcrishikanthc

verification-before-completion

Run validation commands and inspect outputs before claiming completion.

Community
Intermediate