skills.rest
datasciencemonkey
datasciencemonkeyCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Execute verification commands and validate output before claiming completion.

27|9|Updated Feb 3, 2026
Search Tags:#verification#build#quality#evidence#claims#pull-request#tests
One-click install
npx skills add https://github.com/datasciencemonkey/claude-code-cli-bricks --skill verification-before-completion-datasciencemonkey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/datasciencemonkey/claude-code-cli-bricks/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/datasciencemonkey/claude-code-cli-bricks --skill verification-before-completion-datasciencemonkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces verification before claiming completion or success, ensuring honesty and evidence-based reporting in software workflows.

Core Features & Use Cases

  • Mandatory verification step: Requires executing a verification command and reviewing its output before making a completion claim.
  • Scope of application: Applies during code changes, builds, tests, and PR approvals to prevent premature statements.
  • Evidence-driven decisions: Produces a verifiable trail of outputs to back assertions about the state of work.

Quick Start

Run the verification command before claiming completion, then validate that the output confirms success before reporting it.

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 build verification before claiming a pull request is complete?▼

Verification before completion requires running a dedicated verification command, capturing its full output and exit status, and validating the results against predefined criteria before claiming a pull request is complete.

What is evidence-based reporting in software development workflows?▼

Evidence-based reporting in software development is the practice of producing a verifiable trail of command outputs and exit statuses to back assertions about the state of code changes, builds, and tests before reporting success.

How do I prevent premature completion claims during code changes and tests?▼

You prevent premature completion claims during code changes and tests by executing a verification command, reviewing its output to confirm success, and reporting evidence only after validating the results against your criteria.

Does this verification process require specific test frameworks or dependencies?▼

No specific test frameworks or dependencies are required. This verification process applies a mandatory verification step to any command execution, capturing output and exit status to validate results across software workflows.

Why does my build verification fail to prevent false success claims in PR approvals?▼

Build verification fails to prevent false success claims if you do not validate the command's exit status and output against strict criteria before reporting completion, which is required to ensure honesty in pull request approvals.

Related Skills

Explore More Software Engineering Skills→
danieldekaydanieldekay
1

verification-before-completion

Enforce evidence-backed verification of tests, linting, and builds before completion.

Community
Advanced
haryelramalhoharyelramalho

verification-before-completion

Enforces evidence-based verification before any completion claim is made.

Community
Intermediate
bobmatnycbobmatnyc
146

Requesting Code Review

Dispatch a code-reviewer subagent to review changes against plans and requirements.

Community
Basic
randalmurphalrandalmurphal

Orchestration Workflow

Select and execute orchestration commands based on task complexity.

Community
Advanced