test-guided-bug-detector

Analyze failing test results to localize and identify software bugs.

1|2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/santosomar/general-secure-coding-agent-skills --skill test-guided-bug-detector-santosomar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-guided-bug-detector
Source: https://github.com/santosomar/general-secure-coding-agent-skills/tree/main/skills/debugging/test-guided-bug-detector
Command: npx skills add https://github.com/santosomar/general-secure-coding-agent-skills --skill test-guided-bug-detector-santosomar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly identify the root cause of software bugs by analyzing patterns in failing test cases, significantly reducing debugging time.

Core Features & Use Cases

  • Failure Triage: Categorizes test failures based on patterns (single failure, shared error, different errors, etc.) to suggest likely causes.
  • Spectrum-Based Fault Localization: Implements a classic algorithm to rank code lines by their likelihood of containing the bug based on test execution coverage.
  • Failure Clustering: Groups similar failures together to address one bug at a time, preventing wasted effort.
  • Use Case: When a pull request causes 50 tests to fail, this Skill can analyze the failures, identify that 40 of them share a common KeyError, and pinpoint the likely faulty line in a shared fixture, allowing for a quick fix.

Quick Start

Use the test-guided-bug-detector skill to analyze the recent test failures and identify the root cause.

Frequently Asked Questions about test-guided-bug-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pinpoint the root cause of test failures in my code?

You can pinpoint the root cause of test failures by analyzing test execution coverage data and exception stack traces. This approach categorizes failure patterns and applies spectrum-based fault localization to rank code lines by their likelihood of containing the bug.

What is spectrum-based fault localization and how does it work?

Spectrum-based fault localization is a technique that ranks code lines by their likelihood of containing a bug. It works by analyzing test execution coverage data from passing and failing tests to calculate the probability of each line being faulty.

How do I debug multiple failing tests efficiently when a pull request breaks many tests?

To debug multiple failing tests efficiently, you can cluster similar failures together. By grouping failures that share common exception types or stack traces, you can address one root cause at a time and prevent wasted debugging effort.

Can I use failing test results to guide fault localization and bug identification?

Yes, you can use failing test results to guide fault localization by analyzing failure patterns and exception types. This method triages failures into categories like single failure or shared error to suggest likely root causes and pinpoint buggy code.

Do I need test execution coverage data to identify bugs from failing tests?

Yes, test execution coverage data is required to identify bugs from failing tests. The fault localization process analyzes this coverage data alongside exception types and stack traces to accurately pinpoint the root cause of software bugs.

What is the best way to triage test failures by exception type and stack trace?

The best way to triage test failures by exception type and stack trace is to categorize them based on patterns such as single failure, shared error, or different errors. This triage suggests likely causes and groups similar failures for efficient debugging.