skills.rest
KIM-KYOUNG-OH
KIM-KYOUNG-OHCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

issue-bug-report

Convert error logs and stack traces into structured Markdown bug reports.

Updated Feb 9, 2026
Search Tags:#debugging#error-analysis#log-analysis#stack-trace#incident-management#bug-report
One-click install
npx skills add https://github.com/KIM-KYOUNG-OH/dotfiles --skill issue-bug-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-bug-report
Source: https://github.com/KIM-KYOUNG-OH/dotfiles/tree/main/.claude/skills/issue-bug-report
Command: npx skills add https://github.com/KIM-KYOUNG-OH/dotfiles --skill issue-bug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes error logs, stack traces, and system incidents to automatically generate a structured bug report for rapid triage and documentation.

Core Features & Use Cases

  • Automated logging analysis: identifies error type, location, and root cause from logs.
  • Structured report generation: outputs a complete Bug Report Markdown ready for Obsidian vault.
  • Workflow integration: guides next steps and stores results in a centralized repository.

Quick Start

Provide the error logs, stack traces, and reproduction steps to generate a ready-to-submit bug report.

Frequently Asked Questions about issue-bug-report

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

FAQPage Schema
How do I auto-generate structured bug reports from error logs and stack traces?▼

To auto-generate structured bug reports from error logs and stack traces, provide the raw error data and reproduction steps. The system analyzes the incident details and outputs a complete Markdown bug report ready for submission.

What is the best way to document incident context for faster debugging across teams?▼

The best way to document incident context for faster debugging is to enforce a consistent report format. This captures environment context, reproduction steps, and actionable remediation guidance to streamline triage across teams.

How does automated log analysis identify the root cause of a software error?▼

Automated log analysis identifies the root cause of a software error by parsing error logs and stack traces to determine the error type and location. It transforms these incident details into structured documentation for tracking.

Can I use generated bug reports directly in an Obsidian vault for incident management?▼

Yes, you can use generated bug reports directly in an Obsidian vault for incident management. The system outputs a complete Bug Report Markdown format designed for centralized repository storage and team workflow integration.

Do I need to manually format stack traces before generating a bug report?▼

No, you do not need to manually format stack traces before generating a bug report. You simply provide the raw error logs, stack traces, and incident details, and the system automatically enforces a consistent, ready-to-submit report structure.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
phillip-hirschphillip-hirsch

setup-matt-pocock-skills

Configure issue tracker, triage labels, and domain documentation for engineering skills.

Community
Intermediate
rlagycksrlagycks
3

project-guidelines-example

Document project architecture, workflows, code patterns, and testing procedures.

Community
Basic
jayteealaojayteealao

error-analysis

Analyze errors, stack traces, and logs to identify root causes and remediation steps.

Community
Basic