verification-before-completion

Reproduce failures before fixes and confirm resolution with documented evidence.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill verification-before-completion-curdx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/curdx/curdx-flow/tree/main/plugins/curdx-flow/skills/verification-before-completion
Command: npx skills add https://github.com/curdx/curdx-flow --skill verification-before-completion-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents Claude Code from claiming success without reproducing the original failure and verifying the resolution with concrete evidence.

Core Features & Use Cases

  • Reality verification for fix goals: Reproduce the failure before changes and confirm the fix afterward using the same reproduction command.
  • Phase-exit and boundary coverage: Extends verification beyond task-level checks to include commit/tag/release boundaries where regressions can sneak in.
  • Completion and mock-test audit: Validates that tests verify real behavior (not only mock interactions) and that browser/deployment behavior is actually evidenced when required.
  • Evidence documentation in .progress.md: Standardizes how BEFORE and AFTER states are recorded, including expected PASS/FAIL comparisons.

Quick Start

Ask your agent to verify the fix before marking the spec complete, recording BEFORE/AFTER results in the spec’s .progress.md and confirming verificationBlocks evidence.

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 a code fix actually resolves the original failure before marking it complete?

Fix verification requires reproducing the original failure before changes and confirming resolution afterward using the same reproduction command. This ensures you validate fixes with concrete BEFORE/AFTER evidence rather than assuming success without testing.

What's the best way to document before and after results for CI testing and lint reproduction?

Documenting BEFORE/AFTER results in .progress.md standardizes how pre-fix failure and post-fix resolution states are recorded. This includes expected PASS/FAIL comparisons and verificationBlocks evidence for CI tests, type checks, lint, and build reproduction.

Why does my mock test pass but the real browser behavior still fails after deployment?

Mock-test audit validates that tests verify real behavior, not only mock interactions. Browser and deployment behavior must be evidenced with actual verification, ensuring mock quality guardrails catch cases where mocked tests pass but real functionality remains broken.

Can I use automated fix validation for phase-exit and commit boundary checks?

Yes, fix validation extends beyond task-level checks to include commit, tag, and release boundaries where regressions can sneak in. Phase-exit verification applies the same BEFORE/AFTER reproduction logic to catch regressions at critical project milestones.

Does fix verification work with browser and API testing workflows?

Browser and API verification are supported through optional guardrails that evidence actual deployment behavior. The same BEFORE/AFTER reproduction command approach applies, confirming that browser interactions and API responses match expected outcomes after fixes.