Skip to content
Get packs

Test Failure Explorer

Lets an agent import a Vitest 3.2 JSON report and investigate its test failures with cited evidence.

Source Download skill
Repository
QwenLM/qwen-code
Stars
28,880
Licence
Apache-2.0
Files
1 file

What it does

Once installed, when you give the agent an existing Vitest JSON test report, it imports the report as a saved snapshot and answers questions about it: how many tests failed, which files had errors, and what the original diagnostic messages say. It separates facts in the report from guesses about causes, and it can open an interactive view of failures. It does not run your tests itself.

Great for

  • Developers who have a Vitest 3.2 JSON report and want help triaging failures
  • Teams reviewing CI test output after a run without rerunning tests locally
  • People who want the agent to cite specific failed test IDs instead of paraphrasing

Skip it if

  • Projects that do not use Vitest or whose reports are in a different format, since the supported JSON shape is verified only with Vitest 3.2.7
  • Anyone expecting the skill to run tests or fix code, because it only imports and queries reports; a report's pass/fail flag is not proof that a test process actually completed
  • Reports containing sensitive data, since each import writes a workspace-local snapshot file that persists in the project

Try asking

  • “Import reports/vitest-results.json and tell me how many tests failed and in which files”
  • “Show me the failures in the latest Vitest report that mention 'timeout'”
  • “Explain the file-level errors in this report and separate them from failed assertions”
  • “Open an interactive failure view for report reportId abc123 grouped by file”
Step-by-step guide: how to use Test Failure ExplorerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the Apache-2.0 licence and an attribution note.

    test-failure-explorer.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip test-failure-explorer.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip test-failure-explorer.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Provide the workspace-relative path to the JSON report so the import targets the right file
  • Import a newer report explicitly rather than expecting an earlier snapshot to update automatically
  • Ask for the evidence behind a hypothesis and check the cited failure IDs yourself before acting on it

What's inside

  • SKILL.md

Redistributed unmodified from QwenLM/qwen-code under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.