verification-before-completion

Included with Lifetime

$97 forever

Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.

General

What this skill does


# Verification Before Completion

Evidence comes before completion claims. Do not say work is done, fixed,
passing, ready, or complete until a fresh verification command proves it.

## Gate

Before any success claim:

1. Identify the command or checklist that proves the claim.
2. Run the full command now, not from memory.
3. Read the output and exit code.
4. If it fails, report the real state and next action.
5. If it passes, cite the command and result in the report.

## Required Evidence

| Claim | Evidence required |
|-------|-------------------|
| Tests pass | Fresh test command with exit 0 |
| Build passes | Fresh build/type-check command with exit 0 |
| Bug fixed | Reproduction/regression test now passes |
| Requirements met | Checklist mapped to files, tests, or behavior |
| Agent completed | VCS diff reviewed plus verification command |
| Ready to commit/PR | Tests/build relevant to changed surface plus self-review |

## Regression Tests

For bug fixes, a regression test must prove the original symptom:

1. Write or identify the test that fails without the fix.
2. Verify the failure is for the expected reason.
3. Apply the fix.
4. Verify the test passes.

If the project cannot support an automated regression test, document the manual
reproduction steps and why automation was not feasible.

## Output Pattern

```markdown
## Verification

- Command: `npm test -- path/to/test`
- Result: PASS, 12/12 tests, exit 0
- Scope checked: regression test for duplicate email handling
```

Avoid words like "should", "probably", or "looks good" when reporting status.
Use observed results.

Files: 1

Size: 1.8 KB

Complexity: 5/100

Category: General

Source: https://github.com/srstomp/pokayokay/tree/main/plugins/pokayokay/skills/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