bug-workflow

Analyze logs and database states to identify software bug root causes.

Updated Aug 27, 2026

Search Tags:#debugging #troubleshooting #root cause analysis #playwright #bug investigation #task generation

Ready to run

npx skills add https://github.com/N2O-com/N2O-just-workflow --skill bug-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-workflow
Source: https://github.com/N2O-com/N2O-just-workflow/tree/main/02-agents/bug-workflow
Command: npx skills add https://github.com/N2O-com/N2O-just-workflow --skill bug-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and testers systematically investigate and pinpoint the root cause of software bugs, especially when reproduction steps are unclear or when complex system interactions are involved.

Core Features & Use Cases

Root Cause Analysis: Investigates bugs by tracing call chains, analyzing logs, and using temporary end-to-end tests.
Task Generation: Creates actionable tasks for the tdd-agent to implement fixes once the root cause is identified.
Use Case: When a bug is reported that tdd-agent cannot reproduce, bug-workflow can be invoked to perform deep dives into logs, database states, or set up temporary browser tests to capture evidence and identify the underlying issue.

Quick Start

Use the bug-workflow skill to investigate the bug reported in ticket #123.

Frequently Asked Questions about bug-workflow

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

FAQPage Schema

How do I find the root cause of a software bug when reproduction steps are unclear?▼

Root cause analysis for unclear software bugs involves tracing call chains, analyzing logs, inspecting database states, and executing temporary end-to-end tests to capture evidence. This approach systematically investigates complex system interactions to pinpoint the underlying issue.

Can I use Playwright to run temporary browser tests during bug investigation?▼

Playwright can be used to execute temporary end-to-end browser tests during bug investigation. This gathers debugging evidence by simulating user interactions, which is essential for identifying root causes in complex multi-service environments.

What is the best way to investigate bugs in a complex multi-service environment?▼

Investigating bugs in a complex multi-service environment requires analyzing distributed logs, checking database states, and tracing call chains across services. Using browser debugging tools to gather evidence ensures accurate root cause identification.

Does this debugging workflow modify code to fix the identified issue?▼

This debugging workflow focuses strictly on root cause identification rather than code modification. It analyzes logs and database states, then generates detailed tasks for a tdd-agent to implement the actual fixes.

How do I generate actionable tasks for a tdd-agent after identifying a bug?▼

Generating actionable tasks for a tdd-agent requires completing a thorough bug investigation first. Once the root cause is identified through log analysis and temporary tests, detailed implementation tasks are automatically generated for the agent.

When should I use a dedicated bug investigation workflow instead of direct debugging?▼

A dedicated bug investigation workflow is necessary when tdd-agent cannot reproduce a reported bug. It performs deep dives into logs, database states, and uses temporary browser tests to capture evidence that direct debugging might miss.