skills.rest
MiguelAguiarDEV
MiguelAguiarDEVCOMMUNITY
Explore all skills by this author →
Website𝕏@MiguelAguiarDevGitHub

qa-debugging

Guide systematic four-phase root cause debugging for software defects.

Updated Aug 23, 2026
Search Tags:#testing#debugging#troubleshooting#root cause analysis#qa#bug fixing
One-click install
npx skills add https://github.com/MiguelAguiarDEV/baymax --skill qa-debugging-miguelaguiardev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-debugging
Source: https://github.com/MiguelAguiarDEV/baymax/tree/main/skills/qa-debugging
Command: npx skills add https://github.com/MiguelAguiarDEV/baymax --skill qa-debugging-miguelaguiardev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to identify the root cause of bugs, errors, or unexpected behavior before implementing any fixes.

Core Features & Use Cases

  • Systematic Investigation: Guides users through a four-phase process: root cause investigation, pattern analysis, hypothesis and testing, and implementation.
  • Error Prevention: Emphasizes creating failing tests first and verifying no regressions to prevent future issues.
  • Use Case: When a critical bug is reported in production, this Skill can be invoked to ensure the developer follows a rigorous debugging process, preventing quick patches and ensuring a stable, well-understood solution.

Quick Start

Initiate a root cause investigation for the reported bug in the user authentication module.

Frequently Asked Questions about qa-debugging

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

FAQPage Schema
What is systematic root cause debugging and when do I need it?▼

Systematic root cause debugging is a structured approach to identify the underlying cause of software defects before implementing fixes. You need it when a critical bug is reported and you want to avoid quick patches that might introduce regressions.

How do I troubleshoot a software bug without applying a quick patch?▼

To troubleshoot a software bug without a quick patch, follow a four-phase process: root cause investigation, pattern analysis, hypothesis and testing, and controlled implementation. This method emphasizes creating failing tests first to verify the fix.

What is the best way to prevent regressions when fixing production incidents?▼

The best way to prevent regressions during production incidents is to create failing tests first and verify no new issues are introduced. This ensures adherence to safety gates and avoids applying multiple fixes at once.

Can I use this systematic debugging process for any software defect?▼

Yes, you can use this systematic debugging process for any software defect. It applies to scenarios involving bug reproduction, pattern analysis, hypothesis formulation, and the controlled implementation of fixes across your codebase.

Why does my bug fix introduce new errors into the system?▼

Your bug fix likely introduces new errors because it was applied as a quick patch or multiple fixes at once. Following a controlled implementation process with safety gates and failing tests prevents these regressions.

Related Skills

Explore More Software Engineering Skills→
scruffydanscruffydan

systematic-debugging

Identify root causes of software defects through a four-phase debugging workflow.

Community
Intermediate
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate
timurgaleevtimurgaleev
5

investigate

Guide structured root-cause debugging through phases for context, analysis, hypothesis, and verification.

Community
Advanced
CarlosQ96CarlosQ96

hotfix

Create emergency hotfix branches with approvals and rollback documentation.

Community
Advanced