verification-before-completion

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

3|Updated Jul 13, 2020
One-click install
npx skills add https://github.com/nieomylnieja/dotfiles --skill verification-before-completion-nieomylnieja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/nieomylnieja/dotfiles/tree/main/config/agents/skills/verification-before-completion
Command: npx skills add https://github.com/nieomylnieja/dotfiles --skill verification-before-completion-nieomylnieja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claimed completion without verification leads to dishonesty and low-quality outcomes; this Skill enforces evidence-based claims before marking work as complete.

Core Features & Use Cases

  • Discovery of project verification commands (CI workflows, justfile/Makefile targets, and package.json scripts) to define what "done" means.
  • The Gate Function workflow: DISCOVER, IDENTIFY, RUN, READ, VERIFY, ONLY THEN to ensure claims are backed by fresh evidence.
  • Use Case: teams validating PRs, releases, or milestone completions before merging or tagging as done.

Quick Start

Before claiming completion, discover the project's verification commands, run the full verification, review the output, and report the outcome 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 enforce evidence-based verification before claiming a software milestone is complete?

To enforce evidence-based verification, discover your project's verification commands, run the proving command fully, read the output, and only claim completion after verifying the fresh evidence. This prevents dishonest or low-quality completion claims.

What is a Gate Function workflow for CI-CD quality assurance?

A Gate Function workflow for quality assurance defines a strict sequence: DISCOVER verification commands, IDENTIFY the proving command, RUN it fully, READ the output, VERIFY, and ONLY THEN claim success. It ensures completion claims are backed by fresh evidence.

How do I discover verification commands for reproducible QA checks across local environments?

To discover verification commands for QA checks, inspect CI workflows, justfile or Makefile targets, and package.json scripts. Identifying these commands defines exactly what "done" means for your software project before you run full verification.

Does this verification process work for validating pull requests and release tags before merging?

Yes, this verification process works for validating pull requests, releases, and milestone completions. Teams use it to run reproducible QA checks across CI and local environments before merging or tagging work as done.

Why does claimed completion without verification lead to low-quality software outcomes?

Claimed completion without verification leads to low-quality outcomes because it allows unproven code to be marked as done. Enforcing evidence-based claims requires collecting fresh output from proving commands, ensuring software project honesty before merging.