test-guided-bug-detector

Analyze failing test outputs to detect and explain functional bugs.

142|14|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill test-guided-bug-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-guided-bug-detector
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/test-guided-bug-detector
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill test-guided-bug-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers quickly identify the root cause of bugs by analyzing failing test cases, saving significant debugging time.

Core Features & Use Cases

  • Automated Bug Analysis: Analyzes test output, execution paths, and code to pinpoint bug locations.
  • Root Cause Explanation: Provides a clear explanation of the bug mechanism and why the test fails.
  • Fix Suggestions: Offers concrete code changes to resolve the identified bug.
  • Use Case: When a critical test fails unexpectedly, use this Skill to get an immediate analysis of the failure, understand the bug, and receive a suggested fix, rather than spending hours manually debugging.

Quick Start

Use the test-guided-bug-detector skill to analyze the output of the failing test 'test_division_by_zero' from the repository at '/path/to/project'.

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 find the root cause of a failing test case?

To find the root cause of a failing test, this Skill analyzes the test output, execution paths, and repository code to pinpoint suspicious code regions and explain the functional bug mechanism.

Can I get fix suggestions for regression bugs detected during code analysis?

Yes, you can get fix suggestions for regression bugs by providing the failing test output and repository path; the analysis explains the failure mechanism and offers concrete code changes to resolve it.

How does test-guided bug detection explain why my code fails test expectations?

Test-guided bug detection explains failures by comparing actual code behavior against test expectations, processing the execution path to identify the exact suspicious code regions causing the mismatch.

What do I need to provide to debug an unexpected test failure?

To debug an unexpected test failure, you need to provide the specific failing test output and the local repository path so the analysis can process the repository information and pinpoint the bug location.

Are there limitations to using automated bug analysis for complex test failures?

Automated bug analysis relies on the provided failing test outputs and repository information; if the test output lacks execution path details or the bug spans external dependencies, root cause detection may be limited.

What is the best way to investigate a critical test failure?

The best way to investigate a critical test failure is to analyze the specific test output against the repository code, which pinpoints suspicious regions and explains the bug mechanism to suggest a fix.