skills.rest
SPURSGO
SPURSGOCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Execute validation commands and attach outputs as completion evidence.

Updated Aug 23, 2026
Search Tags:#testing#validation#verification#quality-assurance#code-review#pull-request#release-signoff
One-click install
npx skills add https://github.com/SPURSGO/awesome-skills-cn --skill verification-before-completion-spursgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/SPURSGO/awesome-skills-cn/tree/main/verification-before-completion
Command: npx skills add https://github.com/SPURSGO/awesome-skills-cn --skill verification-before-completion-spursgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that teams do not claim completion, a fix, or passing status without verifiable evidence, enforcing a disciplined validation before submission or PRs.

Core Features & Use Cases

  • Validation-first completion: Require executing and reviewing validation commands (tests, builds, lint checks) before declaring completion.
  • Evidence-backed signaling: Attach concrete outputs (logs, exit codes) to completion statements.
  • Use Case: Before merging a feature branch, run the full test suite, build artifacts, and report results; only then publish a completion message.

Quick Start

  1. Activate the skill and run your standard validation workflow.
  2. When ready to declare completion, run the validation suite and attach the outputs as evidence.

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 validation before merging a pull request?▼

To enforce validation before merging a pull request, run your standard validation workflow, capture the command outputs and exit codes, and attach them as evidence to your completion statement before finalizing the branch merge.

What is evidence-backed code review and release sign-off?▼

Evidence-backed release sign-off is a validation-first process where completion claims require concrete outputs like logs and exit codes from test suites and builds, ensuring no feature is declared complete without formal verification.

How do I attach validation command outputs to a completion statement?▼

You attach validation command outputs by executing your testing and build workflows, inspecting the resulting logs and exit codes, and presenting those results as proof within your completion message before deployment.

Can I use this validation skill for feature sign-offs without running a full test suite?▼

No, this validation skill requires running and inspecting validation commands like tests and builds before declaring completion, ensuring every feature sign-off is backed by verifiable execution outputs rather than assumptions.

Related Skills

Explore More Software Engineering Skills→
norrbackanorrbacka

verification-before-completion

Require fresh verification evidence before reporting task completion.

Community
Intermediate
fall-out-bugfall-out-bug
19

deploy

Generate release artifacts and execute GitFlow merge operations for deployments.

Community
Advanced
htafollahtafolla
5

code-review

Analyze code quality metrics and review pull requests for best practices.

Community
Intermediate
MichaelSolatiMichaelSolati

team-qa

Orchestrate game QA cycles with test planning, execution, and sign-off reports.

Community
Advanced