skills.rest
dolutech
dolutechCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Run verification commands and report fresh outputs before declaring completion.

6|Updated Mar 7, 2026
Search Tags:#verification#completion#safety#quality#evidence#code-review#ci
One-click install
npx skills add https://github.com/dolutech/dolu-agents-skills --skill verification-before-completion-dolutech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/dolutech/dolu-agents-skills/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/dolutech/dolu-agents-skills --skill verification-before-completion-dolutech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification leads to false confidence and quality issues. This skill enforces evidence-based status reporting to ensure integrity in software delivery.

Core Features & Use Cases

  • Enforces a structured verification workflow before any success claim.
  • Guides users through identifying the proving command, running it fresh, reviewing outputs, and reporting actual results.
  • Use cases include code completion, build and test status, and deployment readiness checks in CI/CD.

Quick Start

Run the verification workflow to gather fresh evidence (tests, builds, and log outputs) 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 verification before declaring a code task complete?▼

To enforce verification before completion, you must identify a proving command, run it fresh, review the actual outputs, and report the results to prevent misleading success claims.

What is evidence-based status reporting in software delivery?▼

Evidence-based status reporting requires gathering fresh verification data, such as test runs and build logs, before claiming completion to prevent false confidence and ensure quality integrity.

How do I verify build and test status in CI environments?▼

You can verify build and test status in CI environments by identifying the specific proving command, running it fresh, reviewing the output logs, and reporting the actual results auditably.

Does this verification workflow apply to local development environments?▼

Yes, this verification workflow applies to software development tasks across both local and CI environments, ensuring you run fresh tests, lint checks, and builds before reporting completion.

Why does claiming code completion without verification cause quality issues?▼

Claiming code completion without verification causes quality issues by creating false confidence, which evidence-based status reporting solves by requiring a clear, auditable process of fresh test runs and output reviews.

What steps are needed to check deployment readiness in CI/CD pipelines?▼

Checking deployment readiness requires an auditable process: identify the proving command, run it fresh to gather evidence, review the actual outputs, and report the true results before declaring completion.

Related Skills

Explore More Software Engineering Skills→
nieomylniejanieomylnieja
3

verification-before-completion

Guide users to run verification commands and report evidence before completion.

Community
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
srivtxsrivtx

requesting-code-review

Automate pre-commit code verification with security scans and independent review.

Community
Advanced
tizeetizee
2

verification-before-completion

Require fresh verification evidence before declaring code, tests, builds, or tasks complete.

Community
Advanced