skills.rest
carlopezzuto
carlopezzutoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforce verification commands and evidence before marking work complete.

3|1|Updated Nov 5, 2025
Search Tags:#testing#verification#completion#evidence#code-quality#pr#ci
One-click install
npx skills add https://github.com/carlopezzuto/agents --skill verification-before-completion-carlopezzuto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/carlopezzuto/agents/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/carlopezzuto/agents --skill verification-before-completion-carlopezzuto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature completion claims by enforcing verifiable evidence before marking work as done.

Core Features & Use Cases

  • Enforces a step-by-step verification process before claims of completion.
  • Requires running verification commands, reviewing outputs, and capturing evidence.
  • Works across local development and CI pipelines to guard PR readiness and release quality.

Quick Start

Run the designated verification command, review the results, and only then declare completion with 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 prevent premature completion claims for code changes?▼

To prevent premature completion claims, you must enforce verifiable evidence by running a full verification command, reviewing the output, and capturing the results before marking work as done.

How do I verify bug fixes before declaring completion in a CI pipeline?▼

You can verify bug fixes in a CI pipeline by executing verification commands, validating exit codes and outputs, and reporting conclusions with captured evidence before claiming that the work is successfully completed.

What is the best way to enforce evidence-based verification before marking a PR as ready?▼

The best way to enforce evidence-based verification is to implement a step-by-step process that requires running verification commands and reviewing their outputs to guard PR readiness and release quality.

Does this verification process work across local development and CI pipelines?▼

Yes, the verification process works across both local development and CI pipelines to ensure that functional requirements are met and verifiable evidence is captured before declaring success.

Why do I need to review command outputs before claiming a feature is done?▼

You need to review command outputs to validate results and capture verifiable evidence, ensuring that the functional requirements of the feature work are actually satisfied before reporting completion.

Related Skills

Explore More Software Engineering Skills→
bizzybaebizzybae

careful

Validate shell commands for destructive patterns before execution.

Community
Advanced
Eric-Pacheco95Eric-Pacheco95

release-notes

Generate Markdown release notes from merged pull requests, closed tickets, and commit history.

Community
Advanced
MINT-IAMINT-IA

verification-before-completion

Run and inspect verification commands before claiming work completion.

Official
Intermediate
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate