really-done

Included with Lifetime

$97 forever

Verify work before claiming it done. Use when the user says "really done", "are we done", "ready to ship", "ready to commit", "is this passing", or when about to claim work is complete, fixed, or passing. Also use before committing or creating PRs. Requires running verification commands and confirming output before any success claim — evidence before assertions, always.

General

What this skill does


# Really Done

**Evidence before claims, always.** Claiming work complete without verification is dishonesty, not efficiency.

## The Iron Law

```
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
```

If you haven't run the verification command in *this* message, you cannot claim it passes.

## The Gate

Before any status claim or expression of satisfaction:

1. **Identify** the command that proves the claim
2. **Run** it fresh, in full
3. **Read** full output, check exit code, count failures
4. **Verify** output matches the claim
5. **Then** state the claim — with evidence

Skip any step = lying, not verifying.

## What Counts as Proof

| Claim | Requires | Not sufficient |
|-------|----------|----------------|
| Tests pass | Test command: 0 failures | "Should pass" |
| Linter clean | Linter: 0 errors | Partial check |
| Build succeeds | Build: exit 0 | Linter passed |
| Bug fixed | Original symptom test passes | Code changed |
| Regression test works | Red-green-red cycle verified | Test passes once |
| Agent completed | VCS diff shows changes | Agent says "success" |
| Requirements met | Line-by-line checklist | Tests pass |

## Red Flags — STOP

- Hedging: "should", "probably", "seems to"
- Premature satisfaction: "Great!", "Perfect!", "Done!"
- About to commit/push/PR without verification
- Trusting agent success reports
- Partial verification
- "Just this once" / "I'm tired"
- **Any wording implying success without verification**

## Rationalizations vs Reality

| Excuse | Reality |
|--------|---------|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ compiler |
| "Agent said success" | Verify independently |
| "I'm tired" | Exhaustion ≠ excuse |
| "Partial is enough" | Partial proves nothing |

## Patterns

**Tests:** Run → see `34/34 pass` → claim. Not "looks correct".

**Regression (TDD red-green):** Write → run (pass) → revert fix → run (MUST FAIL) → restore → run (pass).

**Build:** Run → exit 0 → claim. Linter passing ≠ build passing.

**Requirements:** Re-read plan → checklist → verify each → report gaps or completion.

**Agent delegation:** Agent reports success → check VCS diff → verify changes → report actual state. Don't trust the report alone.

## When to Apply

Before any:
- Success/completion claim (exact phrase, paraphrase, or implication)
- Expression of satisfaction
- Commit, PR, task completion
- Moving to the next task
- Delegating to agents

## Why It Matters

Past failures: trust broken when the user said "I don't believe you"; undefined functions shipped; incomplete features delivered; time wasted on false completion → redirect → rework. Honesty is a core value.

## Bottom Line

**No shortcuts.** Run the command. Read the output. Then claim the result. Non-negotiable.

Files: 1

Size: 3.3 KB

Complexity: 14/100

Category: General

Source: https://github.com/swissarmyhammer/swissarmyhammer/tree/main/builtin/skills/really-done

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