skills.rest
jnealey88
jnealey88COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Execute verification commands and document outputs as completion evidence.

12|9|Updated Oct 23, 2025
Search Tags:#validation#verification#auditing#evidence#code-review#claims#pr-process
One-click install
npx skills add https://github.com/jnealey88/designsetgo --skill verification-before-completion-jnealey88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/jnealey88/designsetgo/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/jnealey88/designsetgo --skill verification-before-completion-jnealey88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents dishonest completion claims by enforcing a mandatory verification workflow that requires fresh evidence before declaring work complete or merging.

Core Features & Use Cases

  • Enforces a gate: run and validate a defined verification sequence before commit or PR.
  • Documents and attaches verification outputs as evidence to support completion claims.
  • Use Case: teams performing code reviews, QA verification, and release handoffs where verifiable proof of completion is required.

Quick Start

Run the full verification command suite and attach the output as 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 verification before a pull request is merged?▼

Code review verification is enforced by running a defined suite of verification commands, parsing the outputs, and attaching them as documented evidence to meet acceptance criteria before completion.

What is the best way to prevent dishonest completion claims during code reviews?▼

The best way to prevent dishonest completion claims is applying a mandatory verification workflow that executes commands, records outputs, and demands fresh evidence before a PR is approved or merged.

How do I attach verification outputs as evidence for release handoffs?▼

You attach verification outputs as evidence by running the full verification command suite, parsing the results, and documenting them to support completion claims during QA and release handoffs.

Does this verification workflow require specific testing frameworks to run?▼

No specific testing frameworks are required; the workflow executes any defined set of verification commands you configure, parsing the outputs to validate that builds, tests, and deployments meet acceptance criteria.

When do I need to run a defined verification sequence for deployment validation?▼

You need to run a defined verification sequence for deployment validation whenever verifiable proof of completion is required, ensuring fresh evidence is recorded before declaring builds, tests, or deployments complete.

Related Skills

Explore More Content & Communication Skills→
VjayRamVjayRam

dspy-expert

Define DSPy signatures and modules with deterministic evaluation across splits.

Community
Advanced
sachio222sachio222

verification-before-completion

Require fresh verification evidence before claiming completion in pre-commit, pre-PR, and release workflows.

Community
Advanced
growingiogrowingio
91

verification-before-completion

Run automated test commands and analyze output logs to validate code changes.

Official
Intermediate
froggugugugufroggugugugu

code-review

Review code changes for quality, conventions, performance, and security.

Community
Advanced