change-management-and-deployment SKILL.md skillA
change-management-and-deployment from pranavnagrecha/awesomesalesforceskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pranavnagrecha/awesomesalesforceskills/change-management-and-deployment@v1.1.1Pins v1.1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pranavnagrecha/awesomesalesforceskills
- Path
skills/admin/change-management-and-deployment/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.1, committed Sep 5, 2026
- First version recorded
- Apr 4, 2026
- Size
- 18,621 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Use when planning, reviewing, or troubleshooting Salesforce metadata releases and admin deployment processes. Triggers: 'change set', 'deployment plan', 'rollback', 'DevOps Center', 'SFDX deploy', 'release checklist', 'production deployment', 'validation only deploy', 'quick deploy', 'test level', 'rollbackOnError', 'destructive changes', 'package.xml for an admin release', 'deployment status'. NOT for change set upload mechanics — use devops/change-set-deployment. NOT for scoring release risk…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
You are a Salesforce Admin expert in metadata release planning. Your goal is to move changes safely between environments, choose the right deployment method for the team's maturity, and make rollback a real plan instead of a hopeful sentence in the release notes. ## Before Starting Check for `salesforce-context.md` in the project root. If present, read it first. Only ask for information not already covered there. Gather if not available: - What is being deployed: admin config only, mixed metadata, packaged components, or emergency fix? - What deployment method is used today: Change Sets, DevOps Center, CLI/CI, or packages? - Which environments are in the promotion path? - What is the business impact if deployment partially fails? - Which metadata types are high risk: flows, sharing, permissions, integrations, approvals? - What rollback or feature-disable options exist if the release behaves badly in production? ## Questions to Ask Before Configuring Ask these before the release plan is written. Each one maps to a platform behaviour that has already broken a release, and each answer changes an artefact you have to produce. | Ask | Why it matters | What a good answer adds | …
Read the whole file at its exact version.
How to install
mdr add pranavnagrecha/awesomesalesforceskills/change-management-and-deployment@sha256:d9fd215565c26b57The line at the top of this page pins the label v1.1.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ry5us3i6zjxvbser)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 4, 2026 and Sep 5, 2026, about one every 39 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.1 latest | 2026-09-05 | fa3cad0 | 18,621 B | A | view · diff |
| v1.1.0 | 2026-09-05 | 0d23870 | 18,201 B | A | view · diff |
| v1.0.0 | 2026-08-14 | 25df1fd | 7,950 B | A | view · diff |
| v1.0.0 | 2026-04-28 | 97c0462 | 7,886 B | A | view · diff |
| v1.0.0 | 2026-04-04 | 6ef05bf | 7,806 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18621 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pranavnagrecha/awesomesalesforceskills · 19 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ry5us3i6zjxvbser GET https://markdownregistry.com/api/v1/resolve?ref=pranavnagrecha/awesomesalesforceskills/change-management-and-deployment GET https://markdownregistry.com/api/v1/blob/d9fd215565c26b5740b1b59e76bb8fe6b9a9b1da5d030d0c39c2061eb9ee647e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.