diagnose-issues

Orchestrate parallel debug agents to identify root causes of UAT gaps.

Updated Jan 12, 2026

Search Tags:#automation #testing #debugging #software development #root cause analysis #uat

Ready to run

npx skills add https://github.com/sidunrealde/ArchVis --skill diagnose-issues-sidunrealde

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose-issues
Source: https://github.com/sidunrealde/ArchVis/tree/main/.github/skills/diagnose-issues
Command: npx skills add https://github.com/sidunrealde/ArchVis --skill diagnose-issues-sidunrealde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of identifying the root causes of User Acceptance Testing (UAT) failures, preventing guesswork and ensuring targeted fixes.

Core Features & Use Cases

Parallel Debugging: Spawns multiple debug agents simultaneously to investigate different UAT gaps.
Root Cause Analysis: Pinpoints the exact reasons for failures, moving beyond symptoms to underlying issues.
Automated Reporting: Updates UAT documentation with detailed diagnoses and prepares for the planning phase.
Use Case: After UAT identifies several bugs, this Skill will automatically assign a debug agent to each bug, gather their findings, and update the UAT report with the specific code issues and affected files.

Quick Start

Use the diagnose-issues skill to find the root cause for the failed test cases listed in the UAT.md file.

Frequently Asked Questions about diagnose-issues

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

FAQPage Schema

How do I find the root cause of UAT failures in software development?▼

To find the root cause of UAT failures, you can parse UAT gaps and spawn parallel debug agents to investigate each failure, systematically identifying underlying code issues and affected files instead of guessing.

What is the best way to automate debugging for multiple UAT gaps?▼

Automating debugging for multiple UAT gaps is best handled by orchestrating parallel debug agents that investigate different failures simultaneously, collecting diagnostic reports to pinpoint exact root causes and update UAT documentation.

How does parallel root cause analysis work for UAT bugs?▼

Parallel root cause analysis works by spawning specialized debug agents for each UAT gap simultaneously, collecting their diagnostic reports, and updating the UAT documentation with identified root causes and affected files.

Do I need a UAT.md file to debug user acceptance testing failures?▼

Yes, you need a UAT.md file or similar UAT documentation listing failed test cases to parse UAT gaps, spawn debug agents, and update the report with identified root causes and affected files.

Can I use automated debugging before planning fixes for UAT failures?▼

Yes, you can use automated debugging before planning fixes by parsing UAT gaps, assigning debug agents to investigate failures, and gathering diagnostic reports to ensure targeted fixes based on identified root causes.