verification-before-completion

Verify commands, output, and results before committing changes.

Updated Apr 1, 2026

Search Tags:#quality assurance #code review #verification #development best practices #commit hygiene

Ready to run

npx skills add https://github.com/aarushlohit/TheRocketProject --skill verification-before-completion-aarushlohit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/aarushlohit/TheRocketProject/tree/main/rocket/shokunin-opencode-powers/skills/superpowers/verification-before-completion
Command: npx skills add https://github.com/aarushlohit/TheRocketProject --skill verification-before-completion-aarushlohit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a robust checklist for verifying work before making claims of completion, ensuring accuracy and honesty in project reporting.

Core Features & Use Cases

Comprehensive Verification: Offers a structured approach to verify work by checking commands, output, and results.
Pre-Commit Verification: Assists developers in identifying and correcting mistakes before committing changes or creating pull requests.
Task Completion Confirmation: Validates that tasks meet the necessary criteria before moving on or delegating.

Quick Start

Run the verify-work command before committing changes to ensure all tasks meet completion criteria.

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 code changes before committing to ensure work completion?▼

Verify code changes before committing by running a structured verification process that checks commands, output, and results. This pre-commit verification identifies mistakes early and requires evidence-based proof of successful execution before advancing.

What is pre-commit verification and why is it needed for development best practices?▼

Pre-commit verification is a rigorous process of checking task completion criteria before creating pull requests. It is needed for development best practices because it ensures accuracy and honesty in project reporting by requiring evidence-based claims over anecdotal satisfaction.

Does a verification checklist work for both software development and general task completion?▼

Yes, a verification checklist works for both software development and general task completion. It validates that any task requiring proof of successful execution meets necessary criteria before you move on or delegate the work.

What's the best way to enforce commit hygiene and prevent incomplete work claims?▼

The best way to enforce commit hygiene is to require a comprehensive verification process that checks commands and validates output before claiming work completion. This approach catches mistakes before changes are committed.

Can I use automated scripts to validate task completion criteria before a pull request?▼

Yes, you can use scripts to automate the validation of task completion criteria before a pull request. Running a verify-work command executes structured checks to confirm all development tasks meet the required proof of execution.

When should I not use a pre-commit verification process?▼

You should not skip pre-commit verification when working on tasks requiring proof of successful execution, but it may be unnecessary for trivial changes. However, for maintaining strict commit hygiene and accurate project reporting, verification is always recommended.