salesforce-devops
Skill0 starsChanged 6 months agoMITView on GitHub
DevOps skills for animuscrm — package.xml sync rules, deployment, retrieval, and CI/CD pipeline reference.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- PranavNagrecha/AwesomeSalesforceSkillstheir own version, first seen Sep 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- PranavNagrecha/AwesomeSalesforceSkills★ 17same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architecture-decision-recordsSkill
- salesforce-adminSkill
- salesforce-code-analyzerSkill
- salesforce-developer-apexSkill
- salesforce-test-overwatchSkill
- skillsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Remove an entire
<types>block: when it has no remaining members - Distinctive: line 30
After updating package.xml, confirm:
- Very specific: line 31
Every metadata file under force-app/main/default/ has a corresponding entry
- Very specific: line 42
Update manifest/package.xml if any metadata was created or modified (see sync rules above)
- Distinctive: line 60
Check the exit code — if non-zero, read every error message, identify the file and line, fix and re-deploy
- Distinctive: line 65
If Apex classes or triggers were deployed, suggest running tests:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Salesforce DevOps Skill — animuscrm
Covers package.xml maintenance, deployment, retrieval, and CI/CD pipeline behaviour.
Package.xml Sync Rule (MANDATORY)
Whenever you create, rename, or delete any Salesforce metadata file in this project, you MUST update manifest/package.xml to stay in sync.
This applies to every file change — objects, fields, classes, triggers, LWC components, flows, validation rules, permission sets, custom labels, platform events, and all other metadata types.
8 Rules for Editing package.xml
- Always read the current
package.xmlbefore making any modifications - Keep member entries alphabetically sorted within each
<types>block - Keep
<types>blocks alphabetically sorted by their<name>element - Insert new
<types>blocks in the correct alphabetical position when adding a new metadata type - Remove an entire
<types>block when it has no remaining members - Check for duplicates before adding — never create duplicate member entries
- Keep
<version>in sync withsfdx-project.json— currently66.0 - When deleting a metadata file, remove its corresponding
<members>entry from package.xml
Post-Edit Validation
After updating package.xml, confirm:
- Every metadata file under
force-app/main/default/has a corresponding entry - XML uses four-space indentation throughout
- Version element matches
sfdx-project.jsonsourceApiVersion
skill: deploy-and-verify
Trigger phrase: "deploy" / "push to org" / "deploy and verify"
Steps
- Update
manifest/package.xmlif any metadata was created or modified (see sync rules above) - Choose the deploy method:
- Source deploy (most common):
sf project deploy start --source-dir force-app --target-org dev-org --wait 30 - Specific component:
sf project deploy start --metadata <MetadataType>:<ComponentName> --target-org dev-org --wait 30 - Manifest deploy:
npm run deploy:manifest - Validate only (no changes to org):
npm run deploy:validate
- Source deploy (most common):
- Check the exit code — if non-zero, read every error message, identify the file and line, fix and re-deploy
- Verify deployment status:
sf project deploy report - If Apex classes or triggers were deployed, suggest running tests:
npm run test:apex
npm Script Reference
| Script | Command |
npm run deploy | Full source deploy to dev-org |
npm run deploy:validate | Check-only deploy with RunLocalTests |
npm run deploy:manifest | Manifest-based deploy via package.xml |
npm run retrieve | Retrieve all source from dev-org |
npm run test:apex | Run local Apex tests with coverage |
CI/CD Triggers (automatic — no manual action needed)
| Event | What runs |
| Push to feature branch | Nothing (local hooks only) |
| Open/update a PR → main | .github/workflows/validate-pr.yml — check-only deploy + RunLocalTests |
| Merge PR → main | .github/workflows/deploy-main.yml — full deploy + RunLocalTests |
| Manual / nightly 06:00 UTC | .github/workflows/run-tests.yml — test run with coverage |
GitHub Actions Secret Required
The CI workflows authenticate using secrets.SFDX_AUTH_URL. Generate and store it once:
sf org display --target-org dev-org --verbose --json
# Copy "sfdxAuthUrl" value → GitHub repo → Settings → Secrets → SFDX_AUTH_URLDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

