verification-before-completion

Verify completion claims by executing and confirming command outputs before commits.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/jchildree/The-QUESTION --skill verification-before-completion-jchildree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/jchildree/The-QUESTION/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/jchildree/The-QUESTION --skill verification-before-completion-jchildree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures accuracy and honesty in the completion of work by requiring verification steps to be followed before making any success claims.

Core Features & Use Cases

  • Pre-Completion Verification: Mandates execution and confirmation of verification commands before making completion claims.
  • Evidence-Based Reporting: Encourages recording and checking the results of verification steps to provide proof of completion.
  • No shortcuts: Emphasizes the importance of running verification commands fresh each time and verifying results before making claims of success.

Quick Start

Run the verification commands and confirm output before committing or creating PRs.

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 completion before committing or creating a pull request?

Pre-completion verification prevents inaccurate success claims by requiring you to execute specific verification commands and confirm their outputs before committing code or marking milestones complete.

What is evidence-based reporting for task completion?

Evidence-based reporting requires recording and checking the results of verification steps to provide concrete proof that project milestones and code commits are fully complete.

How do I enforce a quality assurance process before claiming a task is done?

You can enforce quality assurance by mandating that fresh verification commands are executed and their outputs verified each time, preventing shortcuts before any completion claim is made.

Can I use previous verification results to prove task completion?

No, this verification process emphasizes running verification commands fresh each time and verifying their results before making claims of success, preventing reliance on outdated outputs.

Does pre-completion verification work for project milestones beyond code commits?

Yes, pre-completion verification applies to code commits, task completion, and any project milestone by requiring verified evidence to back all work completion claims.