Debugging Report

Diagnose failing tests and generate reproducible debugging reports with steps and fixes.

1|2|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill debugging-report-madrid1011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Debugging Report
Source: https://github.com/MAdrid1011/Zircon-VLIW/tree/main/.claude/skills/debug-report
Command: npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill debugging-report-madrid1011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured approach to debugging failing tests by turning observations into a clear, reportable issue that guides reproduction and resolution.

Core Features & Use Cases

  • Backtrace failures to their root cause with contextual information about the test, inputs, and environment.
  • Generate a reproducible, GitHub-ready bug report that documents steps, observed results, expected behavior, and suggested fixes.
  • Facilitate faster triage by organizing findings into a concise, shareable format for developers and QA.

Quick Start

Analyze the failing test, collect context, and generate a reproducible debugging report with steps, inputs, observed versus expected results, and recommended fixes.

Frequently Asked Questions about Debugging Report

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

FAQPage Schema
How do I generate a bug report from a failing test?

Generate a bug report from a failing test by extracting test names, stack traces, input values, and environment details to document reproduction steps, observed versus expected outcomes, and recommended fixes.

What is the best way to trace a test failure back to its root cause?

The best way to trace a test failure to its root cause is to backtrace the failure using contextual information about the test, inputs, and environment to guide developers toward rapid resolution.

How do I create reproducible steps for a bug report from a stack trace?

Create reproducible steps for a bug report from a stack trace by extracting backtrace data, input values, and environment details to clearly document the actions leading to the observed versus expected outcomes.

Can I use this debugging report approach for any codebase?

Yes, you can apply this debugging approach to test failures across codebases by extracting contextual information and organizing findings into a concise, shareable format for developers and QA.

Does generating debugging reports expose sensitive data from my environment details?

Generating debugging reports ensures no leakage of sensitive data while extracting environment details and input values, providing a safe, structured approach to document test failures and recommended fixes.