skills.rest
aRustyDev
aRustyDevCOMMUNITY
Explore all skills by this author →
Website𝕏@aRustyDevGitHub

verification-before-completion

Require fresh verification evidence before reporting completion statuses.

Updated Jan 28, 2026
Search Tags:#verification#build#evidence#code-review#CI#claims
One-click install
npx skills add https://github.com/aRustyDev/git-atomic --skill verification-before-completion-arustydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/aRustyDev/git-atomic/tree/main/.claude/skills/method-verification-dev
Command: npx skills add https://github.com/aRustyDev/git-atomic --skill verification-before-completion-arustydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unverified completion claims by requiring fresh verification evidence before reporting progress or success.

Core Features & Use Cases

  • Gate the claim process: require running verification commands and inspecting full outputs before declaration.
  • Repeatable protocol: follow identify → run → read → verify → report steps to ensure consistency.
  • Use cases: code reviews, PR approvals, CI pipelines, and deployment gating where claims must be backed by evidence.

Quick Start

Identify the verification command that proves success, run it fresh, and review the complete output before making any claim. Capture the evidence (logs, exit codes, artifacts) and attach it to your status update.

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 evidence before marking a build or PR as complete?▼

To enforce verification evidence before completion, you must run the verification command fresh, inspect the full output, and attach the logs or exit codes to your status update before claiming success.

What is the step-by-step process for requiring build evidence in CI pipelines?▼

The step-by-step process for requiring build evidence involves five steps: identify the verification command, run it fresh, read the complete output, verify the results, and only then report the claim with attached evidence.

Does this verification protocol work for deployment gating and code reviews?▼

Yes, this verification protocol works for deployment gating and code reviews by demanding fresh verifiable results and output reports before any status updates or approvals are issued.

Why should I gate PR approvals on fresh verification evidence instead of previous build logs?▼

You should gate PR approvals on fresh verification evidence to prevent unverified completion claims, ensuring that status updates are backed by newly generated results rather than outdated or stale build logs.

What's the best way to prevent unverified completion claims in a software engineering workflow?▼

The best way to prevent unverified completion claims is to follow a repeatable identify, run, read, verify, and report protocol that demands output and failures be documented with evidence before success is declared.

Related Skills

Explore More Software Engineering Skills→
tyk-labtyk-lab

verification-before-completion

Run the full verification command and report exit codes and logs.

Community
Intermediate
RysnzRysnz
1

verification-before-completion

Run verification commands and report completion status with evidence.

Community
Advanced
chiruu12chiruu12
1

autoplan

Run multiple review skills sequentially with auto-decisions and a final approval gate.

Community
Advanced
wesleyegbertowesleyegberto
3

java-spring-boot-verification-loop

Automate end-to-end verification of Spring Boot projects to gate PRs and releases.

Community
Advanced