skills.rest
ayazhankadessova
ayazhankadessovaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug-report

Diagnose failing tests by tracing root causes and generating structured reports.

Updated Feb 9, 2026
Search Tags:#code quality#testing#debugging#troubleshooting#root cause analysis#error reporting
One-click install
npx skills add https://github.com/ayazhankadessova/essential-skills --skill debug-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-report
Source: https://github.com/ayazhankadessova/essential-skills/tree/main/plugins/essential-skills/skills/debug-report
Command: npx skills add https://github.com/ayazhankadessova/essential-skills --skill debug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, step-by-step process to effectively diagnose and report on failing tests, preventing wasted time and ensuring clear communication when issues arise.

Core Features & Use Cases

  • Systematic Debugging: Guides users through a logical sequence of actions to pinpoint the root cause of test failures.
  • Instrumentation: Advises on adding temporary logging to identify specific code paths and variable states.
  • Escalation Protocol: Defines a clear format for reporting issues when stuck, ensuring all necessary information is provided.
  • Use Case: When a critical test in your CI pipeline fails, use this skill to methodically trace the error, add debugging output, and generate a concise report for the development team.

Quick Start

Follow the debugging steps to diagnose the failing test and report the findings.

Frequently Asked Questions about debug-report

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

FAQPage Schema
How do I systematically debug failing tests to find the root cause?▼

To debug failing tests systematically, trace the root cause by following a defined debugging sequence, add instrumentation to log variable states, and escalate with a structured report to pinpoint and communicate test failures efficiently.

What is the best way to report test failures when I am stuck debugging?▼

The best way to report test failures when stuck is to use an escalation protocol that generates a structured report, ensuring all necessary observations and debugging context are clearly communicated to the development team.

How do I add instrumentation to identify specific code paths during troubleshooting?▼

To identify specific code paths during troubleshooting, add temporary logging instrumentation to track variable states and execution flow, allowing you to methodically trace the error source within your software development workflow.

Can I use this systematic debugging approach for CI pipeline test failures?▼

Yes, you can use this systematic debugging approach for CI pipeline test failures. It guides you to methodically trace the error, add debugging output, and generate a concise report for your development team.

What should I do if my test failure root cause analysis is not working?▼

If your root cause analysis is not working, follow the defined debugging sequence to add temporary logging, verify variable states, and escalate the issue using a structured report format to ensure clear communication.

Related Skills

Explore More Software Engineering Skills→
lewinglewing
4

ci-analysis

Analyze Azure DevOps and Helix CI failures for dotnet repository PRs.

Community
Advanced
first-flukefirst-fluke
1

oma-debug

Diagnose code bugs by guiding reproduction, root cause analysis, and regression testing.

Official
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
softsparksoftspark
161

debug

Parse error output into structured diagnostics for root-cause analysis.

Community
Advanced