verification-before-completion

Run verification commands and validate exit codes before claiming task completion.

18|8|Updated May 31, 2023

Search Tags:#code quality #testing #verification #completion #evidence #process enforcement

Ready to run

npx skills add https://github.com/jpmorgan-payments/embedded-finance --skill verification-before-completion-jpmorgan-payments

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/jpmorgan-payments/embedded-finance/tree/main/.github/skills/superpowers/verification-before-completion
Command: npx skills add https://github.com/jpmorgan-payments/embedded-finance --skill verification-before-completion-jpmorgan-payments

SYSTEM DOCUMENTATION & REQUIREMENTS

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 before declaring a task, bug fix, or feature complete.
Evidence-Based Claims: Requires tangible output and exit codes as proof of correctness, not just assumptions or past results.
Use Case: Before committing code, running the test suite and linter is mandatory. If tests fail or linters report errors, the claim of "completion" is invalid until these are resolved and re-verified.

Quick Start

Run the verification command and confirm its output before claiming the work is complete.

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 code verification before claiming a task is complete?▼

Enforce code verification by implementing a strict protocol that requires running specific commands and validating exit codes before any completion claims are made, ensuring evidence precedes assertions.

What is evidence-based completion in software development?▼

Evidence-based completion is a rigorous process requiring tangible command output and exit codes as proof of correctness, preventing premature claims of success and maintaining honesty in task completion.

Why should I run test suites and linters before committing code?▼

Run test suites and linters before committing code to generate mandatory verification evidence, ensuring that if tests fail or linters report errors, the completion claim remains invalid until resolved and re-verified.

How do I prevent shipping incomplete code with automated process enforcement?▼

Prevent shipping incomplete code by applying mandatory process enforcement that blocks success assertions until all verification steps are executed and validated, addressing the risks of costly errors.

Can I use verification commands for agentic task completion?▼

Verification commands are suitable for agentic task completion, satisfying the need for rigorous, repeatable verification steps to ensure automated processes validate work output before declaring success.