skills.rest
scruffydan
scruffydanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Run verification commands and report results with evidence before completion.

Updated Dec 15, 2025
Search Tags:#verification#completion#release#evidence#quality-assurance#code-review#tests
One-click install
npx skills add https://github.com/scruffydan/AI-Agents --skill verification-before-completion-scruffydan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/scruffydan/AI-Agents/tree/main/source/skills/verification-before-completion
Command: npx skills add https://github.com/scruffydan/AI-Agents --skill verification-before-completion-scruffydan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces evidence-based completion by requiring fresh verification before any success claim.

Core Features & Use Cases

  • Guarantees verification before marking work complete, reducing risk of premature releases.
  • Integrates with tests, linting, builds, and reviews to provide a repeatable completion checkpoint.
  • Useful in software delivery, code reviews, and PR workflows to ensure accountability and traceability.

Quick Start

Identify the verification commands for your project, run the full verification sequence (execute, read, verify), and report results with explicit evidence before claiming completion.

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 checks before marking a pull request as complete?▼

You can enforce verification checks by defining required commands for tests and linting, capturing their outputs, and reporting conclusions with supporting evidence before claiming pull request completion.

What is evidence-based completion in software delivery workflows?▼

Evidence-based completion requires running fresh verification commands and capturing their actual outputs before any success claim, ensuring software delivery accountability and reducing the risk of premature releases.

How do I require fresh test and lint results before approving a code review?▼

To require fresh test and lint results, configure a verification sequence that executes the commands, reads the outputs, and evaluates the results to provide a repeatable completion checkpoint for code reviews.

Can I integrate quality assurance checks into my existing PR workflows?▼

Yes, quality assurance checks integrate into PR workflows by running the full verification sequence and reporting explicit evidence, ensuring traceability and accountability before work is marked complete.

What is the best way to prevent premature releases during software development?▼

The best way to prevent premature releases is to enforce a checkpoint that requires running fresh verification commands and evaluating their outputs before allowing any work to be marked complete.

Why does verification before completion matter for release evidence?▼

Verification before completion matters because it captures fresh test and lint outputs, guaranteeing actual results back any success claim and providing the evidence needed for reliable releases.

Related Skills

Explore More Software Engineering Skills→
J-PsterJ-Pster
291

verification-before-completion

Enforces fresh verification evidence before allowing completion claims in builds, tests, lints, or migrations.

Community
Advanced
CodySwannGTCodySwannGT
3

git-commit-submit-pr-deploy-and-verify

Create conventional commits, submit a pull request, and verify deployment success.

Community
Advanced
gujiachun-rainbowgujiachun-rainbow
8

Verification Before Completion

Run verification commands and report exit codes before completion claims.

Community
Advanced
AdeptMindAdeptMind

acceptance-validator

Validate completed development work against acceptance criteria and architectural designs.

Official
Advanced