skills.rest
joseph-c-mcguire
joseph-c-mcguireCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bug-investigation

Log errors, create reproducible test cases, identify root causes, and implement fixes.

1|Updated May 31, 2026
Search Tags:#workflow#TDD#root cause analysis#bug investigation#bug reporting
One-click install
npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill bug-investigation-joseph-c-mcguire
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-investigation
Source: https://github.com/joseph-c-mcguire/spec-driven/tree/main/.cursor/skills/bug-investigation
Command: npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill bug-investigation-joseph-c-mcguire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill aids in the efficient identification, investigation, and documentation of bugs in software systems, simplifying the debugging process and promoting clearer communication among team members.

Core Features & Use Cases

  • Canonical Workflow: Defines a standardized approach for handling bugs, encompassing logging, reproducibility, root cause analysis, and fix implementation.
  • Multi-Artifact Support: Facilitates the creation of a bug report, reproducible test case, and fix implementation for each bug.
  • Interactive Questions: Uses interactive interview questions to guide the user through the process of identifying and fixing bugs.

Quick Start

Start the bug-investigation skill with 'bug-investigation'.

Frequently Asked Questions about bug-investigation

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

FAQPage Schema
What is the best way to structure a bug investigation workflow for software development?▼

A structured bug investigation workflow standardizes error logging, reproducible test case creation, root cause analysis, and fix implementation to systematically resolve software bugs and improve team communication.

How do I identify and document a root cause analysis for a reproducible test case?▼

To identify and document a root cause analysis, you create a reproducible test case, isolate the underlying fault, and generate a comprehensive bug report detailing the error logs and fix implementation.

Can I use this structured debugging process for CI/CD pipelines and production hotfixes?▼

Yes, the structured debugging process is suitable for CI/CD pipelines, development environments, and production hotfixes, ensuring comprehensive bug resolution and reproducible test cases across different deployment contexts.

How does root cause analysis work when resolving software bugs?▼

Root cause analysis works by guiding you through interactive interview questions to isolate the underlying fault, create a reproducible test case, and implement a targeted fix for the software bug.

What artifacts do I need to create when reporting and fixing a software bug?▼

Reporting and fixing a software bug requires creating a detailed bug report, a reproducible test case, and the fix implementation, ensuring comprehensive debugging documentation across all three artifacts.

Related Skills

Explore More Software Engineering Skills→
sayalinvidiasayalinvidia

mcore-cicd

Configure and validate Megatron-LM CI/CD pipelines and PR labeling rules in GitLab.

Community
Intermediate
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
Patasse97Patasse97

tdd-guide

Generate tests, analyze coverage, and guide RED-GREEN-REFACTOR workflows across languages.

Community
Advanced
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced