debug-and-report

Analyze logs and code changes to diagnose issues and create Jira tickets.

Updated Mar 31, 2026

Search Tags:#debugging #logs #codebase #jira #root-cause-analysis #ticketing

Ready to run

npx skills add https://github.com/ivanbaha/team-workspace --skill debug-and-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-and-report
Source: https://github.com/ivanbaha/team-workspace/tree/main/.github/skills/debug-and-report
Command: npx skills add https://github.com/ivanbaha/team-workspace --skill debug-and-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly diagnose production and test issues by analyzing logs and codebase context, then create actionable Jira bug tickets.

Core Features & Use Cases

Log analysis and correlation across distributed systems to identify root causes.
Context enrichment by mapping errors to code changes and recent deployments.
Automated Jira ticket generation with findings, suggested fixes, and links to logs and code.

Quick Start

Provide a step-by-step debug report for a production issue by gathering logs, mapping them to code changes, and opening a Jira bug with all findings.

Frequently Asked Questions about debug-and-report

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

FAQPage Schema

How do I analyze logs and code changes to find a root cause for a production issue?▼

To find a root cause, you analyze logs and map stack traces to recent codebase commits. This process reproduces and validates the issue across environments to pinpoint the exact failure point.

How do I create a Jira ticket with reproducible steps from an error log?▼

Creating a Jira ticket from an error log involves summarizing the root cause and mapping log events to code changes. The generated ticket includes reproducible steps, recommended fixes, and links to relevant code.

What is the best way to debug issues across distributed systems using stack traces?▼

Debugging distributed systems requires correlating log events and stack traces across services. By applying context from recent deployments and repository changes, you can identify the origin of the failure.

Can I reproduce test issues across different environments using codebase context?▼

Yes, you can reproduce test issues across environments by applying repository context. Analyzing log events and recent commits allows you to validate the issue consistently before preparing a ticket.

What should a root cause analysis report include for production incidents?▼

A root cause analysis report should include the identified root cause, recommended fixes, potential risks, and reproducible steps. It must also provide direct links to code references, logs, and ticket data.