Verification Before Completion

Run predefined verification commands before committing or creating pull requests.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/cpfcoaching/glowing-palm-tree --skill verification-before-completion-cpfcoaching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Verification Before Completion
Source: https://github.com/cpfcoaching/glowing-palm-tree/tree/main/skills-library/superpowers/debugging/verification-before-completion
Command: npx skills add https://github.com/cpfcoaching/glowing-palm-tree --skill verification-before-completion-cpfcoaching

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps prevent false claims of work completion by automating verification checks before any commitment or progress report.

Core Features & Use Cases

  • Automated Verification: Run predefined verification commands to confirm work success.
  • Claim Confirmation: Only allows claims after successful verification.
  • Use Case: Before submitting a pull request or committing code, this Skill ensures all tests pass and all requirements are met, reducing the risk of faulty code being merged into the main branch.

Quick Start

Run the verification command for your latest changes before committing.

Frequently Asked Questions about Verification Before Completion

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

FAQPage Schema
How do I automate verification checks before committing code?

Automated verification checks execute predefined scripts to confirm work completion before committing. This prevents false claims of success by ensuring all required tests pass and validating outputs prior to creating a pull request.

What is the best way to prevent false claims of work completion in pull requests?

Preventing false claims of work completion requires running automated verification processes before creating pull requests. This approach enforces quality assurance by only allowing progress reports after all predefined checks pass successfully.

How do I run predefined verification commands to confirm code review success?

Running predefined verification commands to confirm code review success involves executing scripts to validate outputs. This ensures all requirements are met before any commitment is made, reducing faulty code merges.

Do I need scripts to execute verification commands for quality assurance?

Executing verification commands for quality assurance requires scripts to run the necessary checks. These scripts validate outputs and confirm that all required conditions are met before work completion is claimed.

Can I use automated verification to ensure tests pass before a code commit?

Automated verification ensures tests pass before a code commit by running predefined checks. It only allows claims of work completion after successful verification, reducing the risk of faulty code in the main branch.