Dx Devops Test Failures Analyze

Translates DevOps Center test failures and Code Analyzer violations into plain English: which file, method, line, what rule broke, and how to fix it. The skill reasons over failure payloads to categorize problems (assertion failures, exceptions, static analysis hits) and prioritizes whether you need to harden the test or fix production code. It can also create a tracked WorkItem to assign the failure to someone, but that's gated behind confirmation. Use it when a run blows up and you want root cause without digging through stack traces, or when you need to explain a quality gate failure to your team. It won't write the fix code, just tell you what's broken and where to look.

skills.sh installs: 5.1K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill dx-devops-test-failures-analyze --agent claude-code

Installs into .claude/skills of the current project.

Files

Analyze DevOps Center Test Failures

Parses a test failure or Code Analyzer violation payload, explains it in plain language, produces prioritized improvement suggestions, and — only on explicit user request — creates a tracked fix work item. Parts 1–2 are pure reasoning (no writes); Part 3 is an optional, confirmation-gated write.

Never expose raw JSON, stack traces, or internal Salesforce error codes to the user. Always translate to file name, method, line, and plain description.

Prerequisites

Parts 1–2 (analysis): If the failure payload is already in context, no prerequisites are needed — this is pure reasoning. If you must fetch the payload yourself, run prerequisites (references/prerequisite-checks.md, Prereqs 1–4) and obtain the execution result via dx-devops-test-suite-run (its polling step).
Part 3 (work item): Run Prerequisites 1–4. You also need a DevopsProjectId to file under and an OwnerId (assignee). See references/work-item-creation.md.