verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: ntaksh42

Run verification commands and analyze outputs before claiming completion.

1|1|Updated Nov 22, 2025

Search Tags:#code quality #testing #verification #completion #honesty #process

Ready to run

npx skills add https://github.com/ntaksh42/agents --skill verification-before-completion-ntaksh42

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ntaksh42/agents/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/ntaksh42/agents --skill verification-before-completion-ntaksh42

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents premature claims of work completion, ensuring that all verification steps are performed before any assertion of success is made, thereby maintaining honesty and preventing costly errors.

Core Features & Use Cases

Mandatory Verification: Enforces running specific verification commands (tests, linters, builds) before any claim of completion.
Evidence-Based Claims: Requires concrete output and exit codes as proof of success, not just assumptions.
Use Case: Before committing code, you must run the unit tests and ensure they all pass, then verify the linter output shows no errors, and finally confirm the build command exits with a status code of 0.

Quick Start

Before claiming any status or expressing satisfaction, identify and run the command that proves the claim, read its full output, verify it confirms the claim, and only then make the claim 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 verification before claiming code completion?▼

To enforce verification before claiming code completion, identify and run specific command-line tools for testing, linting, and building. You must analyze their full output and exit codes to gather concrete evidence before making any assertions of success.

What is the best way to prevent premature claims of work completion in software development?▼

The best way to prevent premature claims of work completion is implementing a strict protocol that requires running verification commands and analyzing their output. This ensures evidence-based claims by demanding concrete exit codes as proof before any satisfaction is expressed.

How do I verify code quality before committing changes?▼

To verify code quality before committing changes, run your unit tests and confirm they pass, check the linter output for errors, and ensure the build command exits with a status code of 0. Only claim success after reviewing this evidence.

Does mandatory verification require specific testing tools or frameworks?▼

Mandatory verification does not require specific testing tools or frameworks. It applies to any command-line tools you use for testing, linting, and building, requiring you to read their full output and verify exit codes before asserting completion.

Why does my development process need a strict completion verification protocol?▼

Your development process needs a strict completion verification protocol to prevent costly errors and maintain honesty. It ensures all verification steps are performed with concrete output evidence before any claims of success or satisfaction are made.