debug-test-failures

debug-test-failures is a skill for Claude Code, Codex from jonlwowski012/copilot-agent-factory. It costs 16 tokens per session (1,849 once invoked), scanned A, original, MIT.

A workflow for investigating and fixing tests that fail. Tests are checks that verify software behaves as expected.

In plain words
What is it for?
Use it to run tests, isolate a failing test, inspect its error, add debugging output, and address flaky failures.
Why use it?
It narrows a failure to the relevant test, error, and assertion instead of requiring the whole test suite to be debugged at once.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to run tests, isolate a failing test, inspect its error, add debugging output, and address flaky failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonlwowski012/copilot-agent-factory/debug-test-failures
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jonlwowski012/copilot-agent-factory --skill debug-test-failures
Clone the repo
git clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factory

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for debug-test-failures

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/debug-test-failures/github.svg)](https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/debug-test-failures)
Your own site
<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/debug-test-failures"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/debug-test-failures/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for debug-test-failures

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/debug-test-failures"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/debug-test-failures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,849 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.01849
Opus 5.5 $0.00006 $0.00740
Sonnet 5.5 $0.00003 $0.00370
Haiku 4.5 $0.00002 $0.00185

Measured 1mo ago against content hash 59345a5c0831, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

debug-test-failures scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skill-templates/1-testing-quality/debug-test-failures/SKILL.md · 322 lines

How it starts

The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Debug Test Failures

When to Use This Skill

This skill activates when you need to:

  • Investigate why tests are failing
  • Debug specific test failures
  • Understand test error messages
  • Fix flaky or intermittent test failures

Prerequisites

This assumes tests are configured and running. Use run-tests skill to execute tests first.

Step-by-Step Workflow

Step 1: Run Tests and Identify Failures

Run tests with verbose output:

# Python
pytest -v

# JavaScript
npm test -- --verbose

# Go
go test -v ./...

Identify the failing test(s):

  • Note the test file and function name
  • Read the error message carefully
  • Check the assertion that failed

Step 2: Run Only the Failing Test

Python (pytest):

pytest tests/test_file.py::test_function_name -v

JavaScript (Jest):

npm test -- tests/example.test.js -t "test name pattern"

Go:

go test -run TestFunctionName -v

Step 3: Add Debug Output

Python - Add print statements:

def test_example():
    result = my_function(input_data)
    print(f"DEBUG: result = {result}")  # Debug output
    print(f"DEBUG: type = {type(result)}")
    assert result == expected

Run with output visible:

pytest -s tests/test_file.py::test_function_name

Python - Use pytest's debugging:

# Drop into debugger on failure
pytest --pdb

# Drop into debugger on first failure
pytest -x --pdb

JavaScript - Add console.log:

test('example', () => {
  const result = myFunction(inputData);
  console.log('DEBUG: result =', result);
  expect(result).toBe(expected);
});

Step 4: Common Failure Patterns

AssertionError / Unexpected Value

Cause: Expected value doesn't match actual value

Debug steps:

  1. Print both expected and actual values
  2. Check data types match (string vs int, etc.)
  3. Check for whitespace, case sensitivity
  4. Verify test data setup

Example fix:

# Before - fails due to extra whitespace
assert result == "hello"

# After - strip whitespace
assert result.strip() == "hello"

Read the full file on GitHub · 322 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 322 lines · 16 tokens per session scan A 59345a5c0831

Subscribe to this mod's changes

debug-test-failures is a skill published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,849 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

4-phase root cause debugging: understand bugs before fixing.

NousResearch/hermes-agent · 16 tokens

langsmith-observability

LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.

davila7/claude-code-templates · 45 tokens

experimental-code-coverage-local-debugger

Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.

chromium/chromium · 59 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

cli-e2e

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

ComposioHQ/composio · 62 tokens

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…

emdash-cms/emdash · 72 tokens