New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Dx Devops Test Failures Analyze

by forcedotcom in forcedotcom/sf-skills

Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement…

Apache-2.0Auto-check passedTesting & QA

Install Dx Devops Test Failures Analyze

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forcedotcom/sf-skills dx-devops-test-failures-analyze --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dx-devops-test-failures-analyze .claude/skills/dx-devops-test-failures-analyze && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dx-devops-test-failures-analyze
GitHub stars
1.1k
Token cost
~1.4k tokens
SKILL.md length
509 words
Files
5 (incl. references)
Skills in repo
251
Repo updated
First seen
Licence
Apache-2.0

At a glance

Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement…

  • Explain failures
  • SKILL.md covers Prerequisites, Part 1 — Classify and explain…, Part 2 — Improvement suggestions and Part 3 — Create a fix work…, plus 1 more section
  • Calls sf
  • Improvement suggestions

What it does

Dx Devops Test Failures Analyze is an agent skill from forcedotcom/sf-skills. Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement suggestions (test-code vs production-code) — then optionally creates a tracked fix WorkItem on explicit request. Analysis is pure reasoning; work-item creation is a confirmation-gated write. Use this skill to explain failures or improvement suggestions, translate Code Analyzer violations, or track a fix as a work item…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/code-analyzer-violations.md`, `references/failure-categories.md` and `references/prerequisite-checks.md`).

It sits in Testing & QA, covering Failing and flaky tests, Translation and Plain language and style rules. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • Explain failures
  • Improvement suggestions
  • Translate Code Analyzer violations
  • Track a fix as a work item

Example prompts

  • “Use the dx-devops-test-failures-analyze skill to analyz DevOps Center test failures and Code Analyzer violations in plain language — failure…”
  • “/dx-devops-test-failures-analyze”

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • sf

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dx Devops Test Failures Analyze loads about 1.4k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 247 tokens; SKILL.md has 509 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~247
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 509 words, ~1,443 tokens.

Download SKILL.mdSave it as .claude/skills/dx-devops-test-failures-analyze/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
dx-devops-test-failures-analyze
description
Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement suggestions (test-code vs production-code) — then optionally creates a tracked fix WorkItem on explicit request. Analysis is pure reasoning; work-item creation is a confirmation-gated write. Use this skill to explain failures or improvement suggestions, translate Code Analyzer violations, or track a fix as a work item. TRIGGER when: a run failed and the user wants root cause; a quality gate failure needs explaining; violations need translating; the user shares a failure payload and asks how to address it; wants to strengthen tests; or wants to create a fix work item, log a remediation, or assign a failure. DO NOT TRIGGER when: the user wants fix code written (use platform-apex-generate) or new test classes authored (use platform-apex-test-generate).
metadata.version
1.0
metadata.domains
Developer Experience
metadata.minApiVersion
67.0
metadata.relatedSkills
dx-devops-test-suite-assignments-configure, dx-devops-test-suite-run, platform-apex-generate, platform-apex-test-generate

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.

Part 1 — Classify and explain each failure

Determine the failure category, then for each failure extract and translate to plain language: offending file/class, method, line number, the rule or assertion violated, and a fix direction (without writing code). Group failures by category if more than one.

CategoryDescription
Assertion failureA test assertion failed (expected vs actual mismatch)
ExceptionAn unhandled exception was thrown
Code Analyzer violationA static-analysis rule was violated (e.g. ApexCRUDViolation)
TimeoutTest exceeded execution time limit
Compile errorClass failed to compile

Output format:

text
Test failure summary:

<N> failure(s) found:

1. [<Category>] `<ClassName>.cls` — `<methodName>()` at line <N>
   What happened: <plain-language description>
   Rule violated: <ruleName or assertion description>
   Fix direction: <plain-language suggestion>

Full category/pattern tables and Code Analyzer rule translations: references/failure-categories.md and references/code-analyzer-violations.md.

Empty / no-data case: If the payload contains no failures or violations, report that clearly (e.g. "No failures found in the provided execution results.") and stop. Do NOT fabricate failures or suggestions.

Show full SKILL.md (243 more words)Show less

Part 2 — Improvement suggestions

Run this after execution completes with failures, not on static source. For each failed test, reason over the failure message (the primary signal) to identify what the test is not handling, then produce a specific, actionable suggestion and a fix location (Test vs Production code). The full failure-pattern → suggestion mapping is in references/failure-categories.md.

text
Test improvement suggestions based on execution results:

`<testMethodName>()` — [Assertion Failure / Exception / etc.]
Failure: "<failure message>"
What this reveals: <plain-language explanation>
Suggestion: <specific, actionable recommendation>
Fix location: Test | Production code

Overall: <N> improvement(s) across <M> failed test(s).

Do not rewrite the test — only describe what needs to change and why. Fix location: Production code indicates a code defect exposed by a sound test (track separately, not a test-quality blocker). Fix location: Test indicates the test needs hardening (setup, assertions, edge cases).

Part 3 — Create a fix work item (optional, on request only)

Trigger only when the user wants to create a fix work item, log a remediation, or assign a failure to a developer. This is a write operation with a mandatory confirmation gate. Follow references/work-item-creation.md for inputs, the subject/assignee/project confirmation gate, the sf data create record --sobject WorkItem call, and error handling.

Use WorkItem (no namespace) — DevopsWorkItem is not a supported sObject in this org version.

If no DevopsProject exists in the org, report that the work item cannot be created until a project is set up — do NOT fabricate a project or proceed.

  • dx-devops-test-suite-run — produces the failure payload (via its polling step) that feeds this skill.
  • dx-devops-test-suite-assignments-configure — assign/strengthen the suites whose tests are failing.
  • platform-apex-generate / platform-apex-test-generate — to actually write fix code or new test classes (out of scope here).

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/dx-devops-test-failures-analyze of forcedotcom/sf-skills.

  • SKILL.md
  • references/code-analyzer-violations.md
  • references/failure-categories.md
  • references/prerequisite-checks.md
  • references/work-item-creation.md

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Dx Devops Test Failures Analyze next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dx Devops Test Failures Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dx Devops Test Failures Analyze this skillforcedotcom/sf-skills1.1k—~1.4kAutomated safety check: PassApache-2.0
Regex Buildermohitagw15856/pm-claude-skills1.4k—~704Automated safety check: PassMIT
Qcsd Cicd Swarmproffesor-for-testing/agentic-qe494—~2.3kAutomated safety check: PassMIT
Verify Tests Catch the Bugdotnet/maui23k—~2.7kAutomated safety check: PassMIT
Handsontable Test Writing Disciplinehandsontable/handsontable22k—~1.3kAutomated safety check: PassCustom licence
Checkindranilbanerjee/digital-marketing-pro8551 repos~4.4kAutomated safety check: NotesMIT

Similar skills

  • Regex Builder

    mohitagw15856/pm-claude-skills

    Build a regular expression from a plain-English description, or explain an existing one.

    1.4k GitHub stars~704 tokensUpdated today
    Testing & QAAuto-check passed

  • Qcsd Cicd Swarm

    proffesor-for-testing/agentic-qe

    A skill your agent uses when enforcing CI/CD quality gates before release, running regression analysis, detecting flaky tests, or assessing deployment readiness in the QCSD Verification phase.

    494 GitHub stars~2.3k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

  • Verify Tests Catch the Bug

    dotnet/maui

    Official

    Confirms that newly added tests actually fail without the fix, auto-detecting UI, device, unit or XAML tests and running the matching runner.

    23k GitHub stars~2.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Handsontable Test Writing Discipline

    handsontable/handsontable

    Keeps tests honest: write them from the requirement, treat the code as the first suspect when a test is red, and refuse every way of faking a passing run.

    22k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Check

    indranilbanerjee/digital-marketing-pro

    Run the unified pre-publish quality gate on marketing content — wraps scripts/eval-runner.py to score hallucination risk, claim substantiation (with --evidence), brand-voice fit (with --brand)…

    855 GitHub starsUsed in 1 repo~4.4k tokens
    Writing & ContentAuto-check: notes

  • Filter Syntax

    microsoft/testfx

    Official

    Reference data for test filter syntax across all platform and framework combinations: VSTest --filter expressions, MTP filters for MSTest/NUnit/xUnit v3/TUnit, and VSTest-to-MTP filter translation.

    1k GitHub starsUsed in 3 repos~1.5k tokens
    Testing & QAAuto-check passed

More from forcedotcom/sf-skills

All 251 skills in this repo

  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated today
    Auto-check: notes

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated today
    Auto-check: notes

  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Dx Devops Test Failures Analyze

What does Dx Devops Test Failures Analyze do?

Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement…. Dx Devops Test Failures Analyze is an agent skill from forcedotcom/sf-skills. Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement suggestions (test-code vs production-code) — then optionally creates a tracked fix WorkItem on explicit request.

When should I use Dx Devops Test Failures Analyze?

Dx Devops Test Failures Analyze fits situations like: explain failures; improvement suggestions; translate Code Analyzer violations; track a fix as a work item.

How do I install Dx Devops Test Failures Analyze in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill dx-devops-test-failures-analyze -a claude-code`. Or copy the skill folder (skills/dx-devops-test-failures-analyze in forcedotcom/sf-skills) into .claude/skills/dx-devops-test-failures-analyze in your project. Claude Code loads it when a task matches its description.

How do I install Dx Devops Test Failures Analyze in Codex?

Run `npx skills add forcedotcom/sf-skills --skill dx-devops-test-failures-analyze -a codex`. Or copy the skill folder (skills/dx-devops-test-failures-analyze in forcedotcom/sf-skills) into .agents/skills/dx-devops-test-failures-analyze in your project. Codex loads it when a task matches its description.

Can I use Dx Devops Test Failures Analyze in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill dx-devops-test-failures-analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dx-devops-test-failures-analyze, .gemini/skills/dx-devops-test-failures-analyze, .github/skills/dx-devops-test-failures-analyze and .opencode/skills/dx-devops-test-failures-analyze in your project.

What does Dx Devops Test Failures Analyze need to run?

Going by SKILL.md and its folder, Dx Devops Test Failures Analyze needs the command-line tools its instructions call (sf).

Does Dx Devops Test Failures Analyze access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dx Devops Test Failures Analyze safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dx Devops Test Failures Analyze use?

Dx Devops Test Failures Analyze is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dx Devops Test Failures Analyze use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Dx Devops Test Failures Analyze?

Skills that share tags, products or a category with Dx Devops Test Failures Analyze: Regex Builder (mohitagw15856/pm-claude-skills, 1.4k stars), Qcsd Cicd Swarm (proffesor-for-testing/agentic-qe, 494 stars), Verify Tests Catch the Bug (dotnet/maui, 23k stars) and Handsontable Test Writing Discipline (handsontable/handsontable, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dx Devops Test Failures Analyze?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.