verification-before-completion

Run verification commands and confirm outputs before declaring task completion.

2|1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/rafaelcalleja/claude-market-place --skill verification-before-completion-rafaelcalleja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/rafaelcalleja/claude-market-place/tree/main/plugins/claudekit-skills/skills/debugging/verification-before-completion
Command: npx skills add https://github.com/rafaelcalleja/claude-market-place --skill verification-before-completion-rafaelcalleja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rushing to mark tasks complete without thorough verification leads to incomplete work, regressions, and rework. This skill enforces a rigorous verification process, ensuring high-quality deliverables.

Core Features & Use Cases

  • Pre-Completion Checklist: Guides through a systematic checklist to ensure all requirements are met before finalization.
  • Test-Driven Verification: Emphasizes testing and validation as integral parts of task completion, not afterthoughts.
  • Quality Assurance Integration: Incorporates QA principles to catch issues early in the development cycle.
  • Risk Mitigation: Reduces the likelihood of delivering faulty or incomplete work, saving time and resources.
  • Use Case: Before deploying a new feature, use this skill to generate a comprehensive verification checklist, ensuring all unit tests pass, integration tests are green, and user acceptance criteria are met.

Quick Start

Use the verification-before-completion skill to generate a checklist for deploying my new web application.

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 that my code changes are complete before committing?

Verification before completion involves running your test suite, linters, and build commands to confirm outputs match expectations. Execute these commands fully, read their results, and verify alignment with your task requirements before declaring work done. This gates your commit or pull request on fresh evidence of success.

What's the best way to catch incomplete work before deployment?

Use a systematic verification checklist before finalizing any task. Run unit tests, integration tests, and build steps to confirm all acceptance criteria are met. This pre-deployment verification catches regressions and missing requirements early, reducing rework and deployment failures.

How can I reduce rework and quality issues in my development process?

Enforce verification as a mandatory gate before task completion. Rather than rushing to mark work done, systematically prove it through test execution and output validation. This risk-mitigation approach identifies faults in the development cycle, not after delivery.

When should I run tests and linters in my workflow?

Run verification commands immediately before commits or pull requests, when work nears completion. This timing ensures fresh evidence from your test suite and build system confirm quality standards are met before code enters the shared codebase.

Can I use verification checklists for different types of tasks?

Yes. Verification before completion applies across task types—feature deployment, bug fixes, refactoring. Tailor your checklist to specific requirements: unit tests for logic changes, integration tests for system interactions, acceptance criteria validation for user-facing work.