skills.rest
cloudbro-kube-ai
cloudbro-kube-aiOFFICIAL
Explore all skills by this author →
GitHub

verification-before-completion

string

14|5|Updated Jan 25, 2026
Search Tags:#workflow#verification#evidence#quality-assurance#code-review#pr-validation
One-click install
npx skills add https://github.com/cloudbro-kube-ai/k13d --skill verification-before-completion-cloudbro-kube-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/cloudbro-kube-ai/k13d/tree/main/skills/superpowers/verification-before-completion
Command: npx skills add https://github.com/cloudbro-kube-ai/k13d --skill verification-before-completion-cloudbro-kube-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent premature completion claims by enforcing verification with fresh evidence.

Core Features & Use Cases

  • Enforces running a full verification command before claiming success.
  • Requires explicit evidence in outputs to validate the claim.
  • Use Case: In PR reviews or deployment checks, ensure tests pass and verifications are attached before marking work complete.

Quick Start

Run the verification sequence and attach fresh evidence before declaring 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 code review and PR validation before marking work complete?▼

PR validation before completion is enforced by running a full verification command and parsing its output for fresh evidence. This ensures test results, linting, and reviews are explicitly attached before any success is declared.

What is the best way to prevent premature completion claims in a software workflow?▼

Preventing premature completion claims requires verifying results with fresh evidence in your software workflow. The mechanism enforces a full verification command run, parses the output, and blocks success declarations until conclusive evidence is provided.

How does evidence-based verification work for QA and project management tasks?▼

Evidence-based verification for QA and project management works by enforcing a full verification command and requiring explicit, fresh output as proof. Teams must confirm test results and reviews before marking any work as complete.

Do I need to run specific test commands to validate task completion?▼

Yes, validating task completion requires running a full verification command to generate fresh evidence. The process specifically parses this output to ensure tests pass and conclusive proof is attached before success is declared.

Can I use this verification approach for deployment checks and PR reviews?▼

Yes, you can use this verification approach for deployment checks and PR reviews. It ensures tests pass and fresh verifications are explicitly attached to the output before marking work complete, preventing premature claims.

Related Skills

Explore More Software Engineering Skills→
oteroweboteroweb

verification-before-completion

Run a five-step verification workflow and report evidence before completion claims.

Community
Advanced
obraobra
269.6k

verification-before-completion

Verify completion claims by running commands and checking output.

Community
Basic
thktthkt
11

test

Execute project tests and analyze code coverage with package managers and linters.

Community
Intermediate
TalonT-OrgTalonT-Org
5

merge-pr

Merge GitHub pull requests into the integration branch with conflict reports.

Official
Advanced