verification-before-completion

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

Verify task completion and bug fix claims before repository commits.

15|1|Updated Feb 15, 2026

Search Tags:#software quality #bug tracking #code verification #commit verification #work claim verification

Ready to run

npx skills add https://github.com/OpenScribbler/syllago --skill verification-before-completion-openscribbler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/OpenScribbler/syllago/tree/main/content/skills/verification-before-completion
Command: npx skills add https://github.com/OpenScribbler/syllago --skill verification-before-completion-openscribbler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that work claims, such as completing a task or fixing a bug, are verified before they are committed or reported. It prevents premature celebrations and incorrect claims.

Core Features & Use Cases

Pre-commit Verification: Verifies the correctness of claims before committing changes to a repository.
Customizable Verification Commands: Allows users to specify verification commands for different scenarios.
Evidence-Based Assertions: Encourages evidence-based assertions and prevents assumptions from being made without evidence.

Quick Start

Before committing your changes, run the verification commands and check the output before making any claims of completion or fix.

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 them to a repository?▼

To verify code changes before committing, run predefined verification commands and review their output. This pre-commit verification process ensures your work claims are backed by evidence, preventing inaccurate task completion or bug fix reports.

What is evidence-based work claim verification in software development?▼

Evidence-based work claim verification requires running specific commands to prove a task is complete or a bug is fixed. It prevents premature celebrations by ensuring developers provide concrete output evidence before reporting changes.

How do I stop premature claims of bug fixes in my development workflow?▼

Stop premature bug fix claims by integrating customizable verification commands into your workflow. Running these commands before reporting completion ensures all assertions are backed by actual output, maintaining high software quality standards.

Can I customize verification commands for different software quality scenarios?▼

Yes, you can customize verification commands for different scenarios. This flexibility allows you to specify exact checks required for various tasks, ensuring accurate commit verification tailored to your specific software quality needs.

When do I need to run commit verification in my software development workflow?▼

You need to run commit verification immediately before reporting changes or committing to a repository. This pre-commit step checks the output of your verification commands to ensure claims of task completion are accurate and evidence-based.

What are the limitations of using predefined verification commands for work claims?▼

The limitation of predefined verification commands is that they require you to manually specify the correct checks for each scenario. Verification only proves the specified commands pass, meaning untested edge cases might still cause issues after committing.