- Home
- Skills
- Agents & Orchestration
- Smart-Diff for Salesforce
Works with the AI Agents you already use
Smart-Diff for Salesforce
Summarize Salesforce metadata changes and audit deployment risks directly from your git diffs.
$9
Smart-Diff for Salesforce
Example session with this skill installed
Summarize the Salesforce metadata changes between main and this branch. Generate a risk report and check for high-risk items.
- Read your context and instructions
- Compiled the smart-diff for salesforce
I am using agent mode to analyze the diff because no LLM provider key was detected in the environment. I have parsed the changes in force-app/ by comparing main to HEAD.
Salesforce Metadata Change Report
Summary of Changes
- Apex Classes: Added
OrderService.clsandOrderServiceTest.clsto handle new discount logic. - Flows: Updated
Opportunity_Closing_Automationto include a new decision node for high-value accounts. - Objects: Added
Discount_Code__ccustom field toOpportunityobject. - Profiles: Modified
Sales_Userprofile; added read/write access to the newDiscount_Code__cfield.
Deployment Risk
| Component | Risk Level | Change Type | Impact |
|---|---|---|---|
Opportunity_Closing_Automation | HIGH | Update | Complex Flow logic change; requires manual testing of decision branches. |
Sales_User.profile | MEDIUM | Field Access | Permission change for Sales User; verify data visibility. |
OrderService.cls | LOW | New | New service class; ensure unit test coverage is above 75%. |
Integration & Security
- No external integration changes detected.
- Secret Check: No credentials found in diff.
Checklist findings not in the summary
| Risk | Component | What to check |
|---|---|---|
| HIGH | flows/Opportunity_Closing_Automation | Verify Flow Interview logs if this handles bulk records. |
1 high-risk change: see Deployment risk.
Next steps
- Review the
Opportunity_Closing_Automationflow logic in the builder. - Run
OrderServiceTestin a sandbox to verify coverage. - Validate the
Sales_UserFLS in a scratch org before deployment.
Connects securely to your tools. The creator never sees your data.
About this skill
Salesforce deployments often feel like a black box of XML changes and hidden side effects. This skill parses git diffs to generate a metadata-aware risk report, ensuring you never miss a destructive profile change or a critical flow update before hitting 'deploy'.
What it does
- Metadata summarization translates complex XML diffs into readable summaries for flows, Apex classes, triggers, and objects.
- Risk assessment flags high-impact changes in profiles, permission sets, and sharing rules that could break security or access.
- Automated auditing compares changes against a predefined checklist to identify missing deployment steps or manual configurations.
- Secret detection automatically redacts credentials or sensitive tokens found within the metadata diff.
- Large diff handling uses a map-reduce approach to process massive releases without hitting context limits.
How it works
- Identify source by locating
sfdx-project.jsonorpackage.xmlto define the metadata scope. - Analyze range by comparing the current branch or PR against the default branch or specific tags.
- Select engine by choosing between the smart-diff CLI (for LLM-integrated workflows) or direct agent analysis.
- Audit and report by cross-referencing findings with a path-based checklist and generating a structured Markdown report.
Frameworks & tools
Built for Salesforce developers using SFDX or Metadata API structures. It integrates with the @mcarvin/smart-diff CLI and works with standard Git workflows and major LLM providers.
Why this beats prompting it yourself
Standard LLMs struggle with the sheer volume and repetitive structure of Salesforce XML files, often hallucinating or missing critical security changes. This skill uses a specialized ruleset and multi-step audit checklist designed specifically for Salesforce metadata patterns.
Use cases
- PR reviews for Salesforce developers to quickly see what actually changed in a massive
force-apppush. - Release notes generation to summarize a sprint's worth of metadata changes for stakeholders.
- Pre-deployment audits to catch high-risk profile or sharing rule modifications before they reach production.
- Integration tracking to identify changes affecting external systems or API endpoints.
Known limitations
Requires a valid Salesforce project structure with either sfdx-project.json or package.xml. Node.js 22.22.1+ is required for CLI mode. Static resource binaries are ignored during analysis.
Requires sfdx-project.json or package.xml. Node.js 22.22.1+ and smart-diff 6.5.0+ required for CLI mode. Skips static resource binaries.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 11 days ago
Requires
Permissions
Allowed Hosts
File Scopes