verification-before-completion

Included with Lifetime

$97 forever

Force verification before claiming success or completion. Prevents false "it works" claims. Triggers when about to say "done", "complete", "works", "fixed", or "the implementation is ready". Requires actually running builds/tests and showing output before claiming success.

General

What this skill does


# Verification Before Completion

Force verification before claiming success or completion. Prevents false "it works" claims.

## Purpose

Claude often claims things "work" or are "complete" without actually verifying. This skill ensures
actual verification happens before any success claim.

## Triggers

Activate this skill when you're about to say ANY of:

- "Done"
- "Complete"
- "Finished"
- "Works"
- "Fixed"
- "The implementation is ready"
- "This should work"
- "I've implemented..."

## NEVER Claim Success Without

### For Code Changes

- [ ] `dotnet build` passes (no errors)
- [ ] `dotnet test` passes (or explicit reason why skipped)
- [ ] No new warnings introduced
- [ ] Actually ran the code and showed output

### For Factual Claims

- [ ] Verified against assertions.yaml
- [ ] WebSearch if claim involves dates/versions/status
- [ ] Source cited

### For "It Works" Claims

- [ ] Actually executed the code
- [ ] Showed the output to user
- [ ] Tested at least one edge case

### For "Bug Fixed" Claims

- [ ] Reproduced the original bug
- [ ] Applied the fix
- [ ] Verified bug no longer occurs
- [ ] Ran regression tests

## Red Flag Thoughts (REJECT THESE)

| If you're about to say... | Stop and... |
|---------------------------|-------------|
| "This should work" | Actually test it |
| "The fix is complete" | Run the build |
| "I've implemented the feature" | Show test output |
| "The bug is fixed" | Reproduce - fix - verify |
| ".NET 10 preview supports..." | WebSearch to verify version |
| "This is the correct approach" | Cite source or run tests |

## Output Format

Before ANY completion claim, show:

```markdown
## Verification Checklist

### Build Status

- [ ] `dotnet build` - [PASS/FAIL]
- [ ] `dotnet test` - [PASS/FAIL/SKIPPED: reason]

### Verification Steps Performed

1. [What you actually did]
2. [What output you saw]
3. [What edge case you tested]

### Confidence

[high/medium/low] - [why]

### Ready to Claim Complete

[YES/NO] - [if NO, what's missing]
```

## Anti-Pattern Examples

**WRONG:**

```text
"I've fixed the null reference bug. The implementation is complete."
[No build run, no test run, no verification shown]
```

**CORRECT:**

```text
"Let me verify the fix...

$ dotnet build
Build succeeded.

$ dotnet test --filter "NullReferenceTests"
Passed! 3/3 tests passing.

Verification complete. The null reference bug is fixed."
```

**WRONG:**

```text
"This React component should render correctly now."
```

**CORRECT:**

```text
"Let me verify...

$ npm run dev
[Shows browser screenshot or console output]

Component renders correctly. Tested:
- Initial load
- Empty state
- Error state

Verification complete."
```

## Integration

This skill is the FINAL checkpoint before claiming completion:

```text
[all other skills] - analysis complete
     |
[implementation] - code written
     |
[verification-before-completion] - THIS SKILL
     |
     +-- Run build
     +-- Run tests
     +-- Show output
     +-- THEN claim success
     |
[Present to user] - "Ready to proceed?"
```

## The Golden Rule

> **If you didn't run it, you don't know if it works.**
> **If you didn't verify it, don't claim it's complete.**

Files: 2

Size: 14.2 KB

Complexity: 20/100

Category: General

Source: https://github.com/aiskillstore/marketplace/tree/main/skills/ancplua/verification-before-completion

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts