# Log To Bug Report Converter

> Parses error logs, stack traces, and test failures into production-ready bug reports.

- Skill: `shreyasbh02/log-to-bug-report-converter` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add shreyasbh02/log-to-bug-report-converter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shreyasbh02/log-to-bug-report-converter/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: ShreyasBh02 (https://skillmd.com/u/shreyasbh02)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/shreyasbh02/log-to-bug-report-converter

---

# Log-to-Bug-Report Converter (RCA Tool)

Turn noisy log dumps into clean, actionable, developer-ready bug reports in Markdown.

## Instructions
1. Ingest unstructured logs, stack traces, Jenkins/GitHub Actions failure outputs, or console dumps.
2. Analyze the root cause by finding the earliest critical exception or logical error.
3. Generate a structured Bug Report containing:
   - **Title**: Clear, concise summary of the issue.
   - **Environment/Context**: Assumptions based on stack trace (e.g., Java version, Spring Boot, OS).
   - **Steps to Reproduce**: Derived logically from the trace/context.
   - **Expected Behavior**: What should have happened.
   - **Actual Behavior**: The exact failure/exception snippet.
   - **Root Cause Analysis (RCA)**: A developer-centric explanation of exactly what line/module failed and why (e.g., NullPointerException at BaseTest.java:45 due to an uninitialized WebDriver).
4. Use standard Markdown format so it can be easily copied to Jira, Azure DevOps, or GitHub Issues.