skills.rest
greglamb
greglambCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Verify software work with fresh command execution and exit-code inspection.

1|Updated Mar 20, 2026
Search Tags:#testing#quality assurance#verification#build validation#regression checks#completion claims
One-click install
npx skills add https://github.com/greglamb/macos-name-tag-app --skill verification-before-completion-greglamb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/greglamb/macos-name-tag-app/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/greglamb/macos-name-tag-app --skill verification-before-completion-greglamb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unverified claims that work is complete, fixed, passing, or ready to commit by requiring fresh evidence before communicating success.

Core Features & Use Cases

  • Evidence-First Verification: Identifies the command or check that proves a specific claim before stating it.
  • Full Result Review: Requires running the complete verification, reading its output, checking the exit code, and counting failures.
  • Scope and Regression Checks: Applies to tests, builds, linters, bug fixes, requirements, delegated work, commits, and pull requests.
  • Use Case: Before reporting that a macOS application build is successful, use the Skill to run the full build command and confirm its output and exit status.

Quick Start

Use the verification-before-completion skill to verify the current implementation and report only claims supported by fresh command output.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a software build before claiming it is complete?▼

To verify a software build before claiming completion, run the full build command fresh, review the complete output, inspect the exit code, and count failures to ensure evidence supports your success claim.

What is evidence-based verification for bug fixes and regression checks?▼

Evidence-based verification for bug fixes and regression checks requires executing fresh commands, reading full output, checking exit codes, and counting failures before reporting that a fix or test suite is passing.

How do I validate requirements and delegated tasks before committing code?▼

To validate requirements and delegated tasks before committing code, run the relevant verification commands, inspect complete output and exit codes, and report only claims directly supported by fresh execution evidence.

Does verification before completion apply to linters and pull requests?▼

Yes, verification before completion applies to linters and pull requests by requiring fresh full-command execution, complete output review, exit-code inspection, and failure counting before stating that linting or PR checks have passed.

Why does my completion claim fail review despite tests passing locally?▼

Completion claims fail review when tests are not re-run fresh; verification requires executing full commands, reading complete output, checking exit codes, and counting failures to prove correctness before reporting success.

Related Skills

Explore More Software Engineering Skills→
matsuyoshi30matsuyoshi30

verify-completion

Auto-discover and execute lint, test, and build commands to verify completion claims.

Community
Advanced
franroafranroa

verification-before-completion

Require full verification command output before reporting completion.

Community
Basic
oteroweboteroweb

verification-before-completion

Run a five-step verification workflow and report evidence before completion claims.

Community
Advanced
droxeydroxey
1

verification-before-completion

Require fresh verification evidence before claiming completion in software delivery workflows.

Community
Basic