debug

Analyze Azurita logs, code, and history to diagnose system errors.

Updated Jun 1, 2024

Search Tags:#workflow #troubleshooting #bug fix #debug #diagnostics #error analysis

Ready to run

npx skills add https://github.com/gustavop-dev/projectapp --skill debug-gustavop-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/gustavop-dev/projectapp/tree/main/.agents/skills/debug
Command: npx skills add https://github.com/gustavop-dev/projectapp --skill debug-gustavop-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured approach for diagnosing bugs, failing flows, or unexpected behaviors within Azurita projects, enabling efficient troubleshooting without modifying code.

Core Features & Use Cases

Issue Investigation: Analyze error messages, stack traces, and recent changes to identify root causes.
Evidence Collection: Read relevant files and dependencies to gather supporting information before hypotheses.
Troubleshooting Guidance: Recommend effective fixes and verification steps based on collected evidence.

Quick Start

Provide error details and suspect behaviors to the debug workflow for an automated diagnosis process.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I debug errors and failures in Azurita workflows?▼

To debug Azurita workflow errors, you provide error details and suspect behaviors to initiate an automated diagnosis process. The system analyzes logs, code, and history to identify root causes without modifying your files.

How does error analysis work for unexpected behaviors in my project?▼

Error analysis works by reading relevant files and dependencies to collect supporting evidence before forming hypotheses. It examines error messages, stack traces, and recent changes to ensure accurate troubleshooting.

Can I use this diagnostics process for development and operations teams?▼

Yes, you can use this diagnostics process for both development and operations teams. It handles investigation scenarios tailored to both groups, ensuring structured troubleshooting across your project lifecycle.

What is the best way to troubleshoot failing flows without modifying code?▼

The best way to troubleshoot failing flows without modifying code is to use an evidence-based diagnosis approach. This method restricts file modifications and requires explicit evidence gathering to safely recommend effective fixes.

Why does the bug fix investigation restrict file modifications?▼

The bug fix investigation restricts file modifications to ensure safety during diagnostics. By preventing changes, it guarantees that root cause analysis relies purely on explicit evidence gathering from logs and code history.