salesforce-incident-rollback

Executes incident-driven rollback and service restoration workflows for Salesforce releases.

1|Updated May 7, 2026

Search Tags:#release management #rollback #incident response #salesforce #service restoration #post-incident

Ready to run

npx skills add https://github.com/amanpraaj/sf-skill-hub --skill salesforce-incident-rollback-amanpraaj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: salesforce-incident-rollback
Source: https://github.com/amanpraaj/sf-skill-hub/tree/main/skills/salesforce/salesforce-incident-rollback
Command: npx skills add https://github.com/amanpraaj/sf-skill-hub --skill salesforce-incident-rollback-amanpraaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a Salesforce release causes a production incident, teams need a structured way to triage impact, choose a safe rollback point, execute the rollback, and verify service restoration without improvising under pressure. ## Core Features & Use Cases - Incident Triage: Classify incident severity to determine the urgency and scope of the response. - Rollback Selection: Use a decision tree to pick the fastest safe rollback path based on severity and data corruption risk. - Recovery Validation: Run smoke checks after rollback and produce a post-incident action list using a structured template. - Use Case: After a Salesforce deployment causes a Sev1 outage with customer impact, follow the workflow to immediately roll back, validate restoration, and document root cause and preventive actions. ## Quick Start Use the salesforce-incident-rollback skill to triage this production incident and execute a safe rollback of the latest Salesforce release.

Frequently Asked Questions about salesforce-incident-rollback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I roll back a Salesforce release after a production incident?▼

Classify the incident severity first, then determine the rollback scope and safe restore point. Execute the fastest safe rollback path, validate restoration with smoke checks, and document the outcome in a post-incident action list.

How to decide when to roll back a Salesforce deployment?▼

Use the rollback decision tree: a Sev1 incident with customer impact triggers an immediate rollback, while data corruption risk requires rollback plus containment. Severity classification drives the urgency and scope of the response.

What should a Salesforce post-incident report include?▼

A post-incident report should include a summary, root cause, recovery timeline, and preventive actions. The skill provides a post-incident template covering these four sections for consistent documentation.

When is rollback not the right response to a Salesforce incident?▼

Rollback may not fit when the issue is isolated, low severity, or fixable with a forward hotfix faster than a full restore. The workflow starts with severity classification and scope determination to avoid unnecessary rollbacks.