verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
What this skill does
# Verification Before Completion **Never declare work complete without running verification commands and confirming their output.** Evidence before assertions, always. ## Core Rule Before claiming ANY of the following, you MUST run the relevant verification commands and confirm their output: - "Tests pass" - "The fix works" - "Build succeeds" - "Everything is green" - "Ready to commit/push/merge" - "Done" / "Complete" / "Finished" ## What Counts as Verification **Acceptable evidence:** - Running the test suite and seeing the output (pass count, zero failures) - Running the build command and seeing "build succeeded" or equivalent - Running typecheck/lint and seeing zero errors - Reproducing the specific scenario that was broken and confirming it now works - Running the specific test that was failing and confirming it now passes **NOT acceptable evidence:** - "I think this works based on the code I wrote" - "This should fix it" (without running anything) - "The logic looks correct" (code reading alone) - Committing without running tests - Declaring done because the implementation matches the plan ## Workflow 1. **Before claiming tests pass:** Run the test command. Read the output. Confirm zero failures. 2. **Before claiming a fix works:** Reproduce the original failure scenario. Confirm it no longer fails. 3. **Before claiming the build succeeds:** Run the build command. Read the output. Confirm no errors. 4. **Before committing:** Run tests + typecheck + lint. All must pass. 5. **Before creating a PR:** Run the full verification suite. Confirm CI-equivalent checks pass locally. ## Red Flags Stop and verify if you catch yourself: - Saying "I believe this works" without having run it - Committing immediately after writing code - Skipping tests because "it's a small change" - Declaring a bug fixed without reproducing the original issue - Saying "tests should pass" instead of "tests pass — here's the output" - Trusting that your code is correct because it looks right ## The Mantra **"Show me the output."** Every claim of completion must be backed by command output you have actually seen in this session.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.