bobmatnyc/verification-before-completion
universal/debugging/verification-before-completion/SKILL.md
Run verification commands and confirm output before claiming success
$ install --global
skillsauthnpx skillsauth add bobmatnyc/claude-mpm-skills verification-before-completionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 4:08 AM157.9s6 files scanned
SKILL.md
- name:
- verification-before-completion
- description:
- Run verification commands and confirm output before claiming success
- user-invocable:
- false
- disable-model-invocation:
- true
- version:
- 2.0.0
- category:
- debugging
- author:
- Jesse Vincent
- license:
- MIT
- source:
- https://github.com/obra/superpowers-skills/tree/main/skills/debugging/verification-before-completion
- summary:
- Evidence before claims: mandatory verification before ANY completion claim
- when_to_use:
- When about to claim work is complete, fixed, passing, or ready. ESPECIALLY before commits, PRs, or task completion.
- quick_start:
- 1. Identify verification command 2. Run FULL command 3. Read complete output 4. Verify results 5. THEN claim with evidence
- context_limit:
- 800
- requires_tools:
- []
Verification Before Completion
Overview
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
This skill enforces mandatory verification before ANY completion claim, preventing false positives, broken builds, and trust violations.
When to Use This Skill
Activate ALWAYS before claiming:
- Success, completion, or satisfaction ("Done!", "Fixed!", "Great!")
- Tests pass, linter clean, build succeeds
- Committing, pushing, creating PRs
- Marking tasks complete or delegating to agents
Use this ESPECIALLY when:
- Under time pressure or tired
- "Quick fix" seems obvious or confidence is high
- Agent reports success or tests "should" pass
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
Without running the verification command in this message, claiming success is not allowed.
Core Principles
- Evidence Required: Every claim needs supporting evidence
- Fresh Verification: Must verify now, not rely on previous runs
- Complete Verification: Full command, not partial checks
- Honest Reporting: Report actual state, not hoped-for state
Quick Start
The five-step gate function:
- IDENTIFY: What command proves this claim?
- RUN: Execute the FULL command (fresh, complete)
- READ: Full output, check exit code, count failures
- VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
- ONLY THEN: Make the claim
Skip any step = lying, not verifying.
Key Patterns
Correct Pattern:
✅ [Run pytest] [Output: 34/34 passed] "All tests pass"
Incorrect Patterns:
❌ "Should pass now"
❌ "Looks correct"
❌ "Tests were passing"
❌ "I'm confident it works"
Red Flags - STOP Immediately
STOP when:
- Using "should", "probably", "seems to"
- Expressing satisfaction before verification
- About to commit/push/PR without verification
- Trusting agent success reports
- Relying on partial verification
ALL of these mean: STOP. Run verification first.
Why This Matters
Statistics from real-world failures:
- Verification cost: 2 minutes
- Recovery cost: 120+ minutes (60x more expensive)
- 40% of unverified "complete" claims required rework
Core violation: "Lying leads to replacement"
Navigation
For detailed information:
- Gate Function: Complete five-step verification process with decision trees
- Verification Patterns: Correct verification patterns for tests, builds, deployments, and more
- Red Flags and Failures: Common failure modes, red flags, and real-world examples with time/cost data
- Integration and Workflows: Integration with other skills, CI/CD patterns, and agent delegation workflows
The Bottom Line
No shortcuts for verification.
Run the command. Read the output. THEN claim the result.
This is non-negotiable.
Related Skills
bobmatnyc/axum
development
VerifiedTrustedCommunity
Axum (Rust) web framework patterns for production APIs: routers/extractors, state, middleware, error handling, tracing, graceful shutdown, and testing
53SKILL.mdUpdated May 19, 2026
bobmatnyc/web-performance-optimization
development
VerifiedTrustedCommunity
Optimize web performance using Core Web Vitals, modern patterns (View Transitions, Speculation Rules), and framework-specific techniques
49SKILL.mdUpdated May 30, 2026
bobmatnyc/api-documentation
development
VerifiedTrustedCommunity
Best practices for documenting APIs and code interfaces, eliminating redundant documentation guidance per agent.
49SKILL.mdUpdated May 30, 2026
bobmatnyc/api-design-patterns
development
VerifiedTrustedCommunity
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices
49SKILL.mdUpdated May 30, 2026