AI-Skills-Collection log-to-bug-report-converter

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

install
source · Clone the upstream repo
git clone https://github.com/ShreyasBh02/AI-Skills-Collection
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ShreyasBh02/AI-Skills-Collection "$T" && mkdir -p ~/.claude/skills && cp -r "$T/log-to-bug-report-converter" ~/.claude/skills/shreyasbh02-ai-skills-collection-log-to-bug-report-converter && rm -rf "$T"
manifest: log-to-bug-report-converter/SKILL.md
source content

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.