agentleFS
animuscrmsfdcanimuscrmsfdc/salesforce-vibe-coding/.claude/skills/salesforce-devops/SKILL.md

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

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
  1. Very specific:

    Remove an entire <types> block: when it has no remaining members

    line 24
  2. Distinctive:

    After updating package.xml, confirm:

    line 30
  3. Very specific:

    Every metadata file under force-app/main/default/ has a corresponding entry

    line 31
  4. Very specific:

    Update manifest/package.xml if any metadata was created or modified (see sync rules above)

    line 42
  5. Distinctive:

    Check the exit code — if non-zero, read every error message, identify the file and line, fix and re-deploy

    line 60
  6. Distinctive:

    If Apex classes or triggers were deployed, suggest running tests:

    line 65

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Always read the current package.xml before making any modifications
  2. Keep member entries alphabetically sorted within each <types> block
  3. Keep <types> blocks alphabetically sorted by their <name> element
  4. Insert new <types> blocks in the correct alphabetical position when adding a new metadata type
  5. Remove an entire <types> block when it has no remaining members
  6. Check for duplicates before adding — never create duplicate member entries
  7. Keep <version> in sync with sfdx-project.json — currently 66.0
  8. 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.json sourceApiVersion

skill: deploy-and-verify

Trigger phrase: "deploy" / "push to org" / "deploy and verify"

Steps

  1. Update manifest/package.xml if any metadata was created or modified (see sync rules above)
  2. 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
  3. Check the exit code — if non-zero, read every error message, identify the file and line, fix and re-deploy
  4. Verify deployment status:
    sf project deploy report
  5. If Apex classes or triggers were deployed, suggest running tests:
    npm run test:apex

npm Script Reference

ScriptCommand
npm run deployFull source deploy to dev-org
npm run deploy:validateCheck-only deploy with RunLocalTests
npm run deploy:manifestManifest-based deploy via package.xml
npm run retrieveRetrieve all source from dev-org
npm run test:apexRun local Apex tests with coverage

CI/CD Triggers (automatic — no manual action needed)

EventWhat runs
Push to feature branchNothing (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_URL

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.