rollback
Revert changes when implementation fails. Use for "rollback", "undo", "revert", "go back", "start over".
What this skill does
# Rollback Manager Safely revert changes when things go wrong. ## Workflow ### 1. Understand Request Ask user: - What went wrong? (bug, wrong approach, want to try different solution) - How far back? (last commit, checkpoint start, specific commit, single file) ### 2. Check State ```bash git status git log --oneline -10 git diff --stat HEAD~5 ``` Show: ``` Current State: - Branch: main - Uncommitted: 2 files modified - Recent commits: abc123 - feat: add form def456 - fix: validation ... ``` ### 3. Identify Target **Rollback to checkpoint start:** ```bash git log --oneline --grep="CP2" ``` **Rollback specific commits:** ```bash git log --oneline -10 ``` **Single file:** ```bash git log --oneline -- src/path/file.tsx ``` ### 4. Preserve Work (Optional) Ask: "Any code to save before rolling back?" If yes: - Create backup branch: `git branch backup-[date]` - Or copy snippets to temp file ### 5. Confirm Before Executing ``` I will run: 1. git stash (save uncommitted) 2. git reset --hard [commit] This will discard changes since [target]. Type 'confirm' to proceed. ``` ### 6. Execute ```bash # Safe methods: git reset --hard [commit] # Clean reset git revert [commit]..HEAD # Preserve history git checkout [commit] -- path/file # Single file ``` ### 7. Update Tracking Update `.planning/CHECKPOINTS.md`: - Mark rolled-back tasks incomplete - Add rollback note ### 8. Verify ```bash bun run build git status ``` ``` Rollback complete! Rolled back to: abc123 - feat: setup Build: Passing Backup: backup-2026-02-01 ``` ## Common Scenarios | Scenario | Command | |----------|---------| | Undo last commit | `git reset --soft HEAD~1` | | Start checkpoint over | `git reset --hard [cp-start]` | | Revert single file | `git checkout [commit] -- file` | | Keep some changes | `git stash` → reset → `git stash pop` | ## Emergency Recovery ```bash git reflog # Find lost commits git checkout [reflog-hash] # Recover ``` ## Rules 1. Always confirm before destructive commands 2. Create backup branch before hard reset 3. Warn about uncommitted changes 4. Test build after rollback
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.