skills.rest
ivanbaha
ivanbahaCOMMUNITY
Explore all skills by this author →
GitHub

Debug & Report

Analyze logs and codebase to diagnose issues and generate Jira tickets.

Updated Mar 31, 2026
Search Tags:#logs#codebase#debug#reporting#jira#root-cause#issue-tracking
One-click install
npx skills add https://github.com/ivanbaha/team-workspace --skill debug-report-ivanbaha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Debug & Report
Source: https://github.com/ivanbaha/team-workspace/tree/main/.agents/skills/debug-and-report
Command: npx skills add https://github.com/ivanbaha/team-workspace --skill debug-report-ivanbaha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze production and test failures by inspecting logs and code context to identify root causes and produce actionable remediation steps.

Core Features & Use Cases

  • Triage incidents by correlating logs, traces, and recent deployments to pinpoint root causes.
  • Generate a structured debug report and a Jira bug ticket with findings, steps to reproduce, and suggested fixes.
  • Integrate with existing issue workflows to streamline triage and resolution.

Quick Start

Provide a concise, actionable debug report for the current incident and create a Jira ticket with all findings.

Frequently Asked Questions about Debug & Report

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

FAQPage Schema
How do I diagnose production issues by analyzing logs and the codebase?▼

Diagnosing production issues involves correlating logs, traces, and recent deployments to pinpoint root causes. It enforces structured data collection and cross-referencing logs with the codebase to identify intermittent failures and deployment anomalies.

Can I automatically generate Jira tickets from debug reports?▼

Yes, you can generate Jira bug tickets directly from debug reports. The system creates structured tickets containing your diagnostic findings, steps to reproduce the issue, and suggested fixes to streamline triage and resolution.

What is the best way to triage intermittent test failures and regressions?▼

The best way to triage intermittent test failures and regressions is by correlating logs with recent deployments. This approach enforces structured data collection and cross-references traces against codebase context to pinpoint the root cause.

How do I find the root cause of a deployment-related anomaly?▼

To find the root cause of a deployment-related anomaly, you cross-reference logs and traces with recent codebase changes. This structured data collection process isolates the regression and produces actionable remediation steps.

Does this issue tracking approach work for test environment failures?▼

Yes, this issue tracking approach works for test environment failures. It analyzes both production and test issues by inspecting logs and code context to identify root causes and generate structured Jira bug tickets.

Related Skills

Explore More Software Engineering Skills→
albertdobmeyeralbertdobmeyer
2

log-analyzer

Analyze application logs to surface errors, exceptions, and root causes.

Community
Intermediate
8GG-Git8GG-Git

fix-ticket

Automate Jira bug fixing from ticket analysis through commit and status updates.

Community
Advanced
RedBoardDevRedBoardDev

pr-summary

Generates PR titles and descriptions from git branch diffs and commit history.

Community
Basic
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced