preview

Included with Lifetime

$97 forever

Use when the user wants diff-before-apply discipline — show what would change, get approval, then apply. Risk-area enforcement. "Preview the change", "show before applying".

General

What this skill does


# preview

Diff-before-apply. AI proposes, user approves, AI applies. Distinct from `/pair` (which is per-step) — preview is per-change.

## Method

1. **Generate the change.** Plan the edits but **do not apply**.
2. **Diff.** Render the proposed diff in unified format. For multi-file changes, group by file.
3. **Surface risk axes** for the user:
   - Files touched
   - LOC delta
   - Tests affected
   - Public API changes
   - Migration concerns
4. **Three options:** Accept, Edit, Reject.
5. **Apply** on accept. **Adjust** on edit (user types deltas; AI integrates). **Drop** on reject.
6. **Verify** post-apply: tests, lint, typecheck.

## Output shape

```
Proposed change:    <one-line goal>

Diff:
  --- src/foo.ts
  +++ src/foo.ts
  @@ -10,5 +10,8 @@
   function foo(x: string) {
  -  return x.length;
  +  if (!x) return 0;
  +  return x.length;
   }

  --- tests/foo.test.ts
  +++ tests/foo.test.ts
  @@ ...

Risk:
  Files:        2
  LOC:          +5 -1
  Tests:        2 added
  Public API:   <none>
  Migration:    <none>

[accept | edit | reject]
```

## Rules

- **Don't apply silently.** Even on small changes, show diff first.
- **Risk axes mandatory.** Surface what could go wrong.
- **Edit mode is collaborative.** User types changes; AI integrates without re-proposing wholesale.
- **Verify post-apply.** Tests must stay green.

## Anti-patterns

- "Looks good?" without showing the diff
- Applying then asking "OK?" (defeats the point)
- Hiding risk axes
- Ignoring user's edits and re-proposing your own version

## When NOT to use

- Trivial change (one comment) — overkill
- User explicitly said "go" — they don't want preview
- High-trust autonomous mode — `/autonomous` (different discipline)

## Subagent dispatch

- None — preview is direct
- Optional: `Plan` if change is complex enough to need design first

## Value over native CC

CC defaults to applying when capable. Preview enforces the propose-before-apply contract. The discipline IS the value.

Files: 1

Size: 2.2 KB

Complexity: 6/100

Category: General

Source: https://github.com/ialameh/sift-coder/tree/main/skills/workflow/preview

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