skills.rest
getspur
getspurOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforces verification of code changes, test results, and build statuses before completion.

2|Updated Apr 15, 2026
Search Tags:#automation#workflow#testing#quality assurance#verification#reliability
One-click install
npx skills add https://github.com/getspur/spur --skill verification-before-completion-getspur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/getspur/spur/tree/main/.spur/skills/verification-before-completion
Command: npx skills add https://github.com/getspur/spur --skill verification-before-completion-getspur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of claiming work is finished without actual proof, ensuring that all assertions of success are backed by verifiable command output.

Core Features & Use Cases

  • Gatekeeping Claims: Forces a rigorous verification step before any status update or PR creation.
  • Evidence-Based Workflow: Mandates the execution of specific commands to confirm test passes, build success, or bug fixes.
  • Use Case: When an agent believes a bug is fixed, this skill requires the agent to run the specific regression test and confirm the output before reporting the fix to the user.

Quick Start

Apply the verification-before-completion skill to validate the current task status by running the necessary test suite and confirming the output before making any completion claims.

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 evidence-based work completion before declaring a bug fix successful?▼

You can enforce evidence-based completion by applying a strict verification protocol that requires running specific regression tests and analyzing the command output before allowing any success declaration.

What is a verification protocol for software development lifecycles?▼

A verification protocol for software development lifecycles is a gatekeeping process that requires empirical evidence from command execution to validate code changes and test results before integration or status updates.

How do I prevent agents from updating a PR status without running tests?▼

Prevent premature status updates by mandating the execution of specific test suites and confirming the output passes before any PR creation or work completion claim is accepted.

Does this verification approach work for automated quality assurance workflows?▼

Yes, this approach fits automated quality assurance workflows by satisfying the requirement for objective proof of correctness through fresh execution and output analysis during the workflow.

What are the limitations of mandating fresh execution for build status validation?▼

The limitation of mandating fresh execution for build status validation is that it requires running the necessary test suite and command output analysis every time, which may increase workflow duration before completion claims are accepted.

Related Skills

Explore More Software Engineering Skills→
tpntpn
97

improved-ui

Guide users through the PerfectHash UI for command generation and build workflows.

Community
Intermediate
ReinaMacCredyReinaMacCredy

maestro:verification

Enforce build, test, and lint verification before completion claims.

Community
Advanced
abhishekdutta18abhishekdutta18

browser-qa

Automate visual, functional, and accessibility testing of web pages.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced