gh-issue-bug

Generate structured GitHub bug reports in Markdown from conversation context.

43|21|Updated Jun 3, 2025
One-click install
npx skills add https://github.com/blockscout/mcp-server --skill gh-issue-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue-bug
Source: https://github.com/blockscout/mcp-server/tree/main/.claude/skills/gh-issue-bug
Command: npx skills add https://github.com/blockscout/mcp-server --skill gh-issue-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of structured bug reports for GitHub issues, transforming conversational details into a standardized format.

Core Features & Use Cases

  • Structured Bug Reporting: Generates detailed bug reports with sections for description, reproduction steps, expected/actual behavior, root cause, and suggested fixes.
  • Automated Filenaming: Creates filenames based on the current date and a short issue name for easy organization.
  • Use Case: When a bug is discussed in a chat, invoke this skill to quickly draft a comprehensive bug report that can be directly used for a GitHub issue.

Quick Start

Use the gh-issue-bug skill to generate a bug report for the issue discussed.

Frequently Asked Questions about gh-issue-bug

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

FAQPage Schema
How do I generate a structured GitHub bug report from a conversation?

To generate a structured GitHub bug report, provide the conversational context detailing the issue. The skill automatically extracts bug details, reproduction steps, expected and actual behavior, and suggested fixes into a standardized Markdown format.

What is the best way to format extracted bug details for GitHub issue tracking?

The best way to format bug details for GitHub issue tracking is using a standardized Markdown structure. This includes dedicated sections for the description, reproduction steps, expected vs. actual behavior, root cause analysis, and suggested fixes.

Can I automate bug report generation for GitHub issues from chat discussions?

Yes, you can automate bug report generation by invoking the skill during a chat discussion. It processes the conversational context to draft a comprehensive bug report that can be directly used for a GitHub issue.

Does the GitHub bug report generator require a specific file naming convention?

Yes, the GitHub bug report generator requires a date-based filename convention. It automatically creates filenames using the current date and a short issue name to ensure easy organization of your bug reports.

What sections are included in an automated GitHub bug report?

An automated GitHub bug report includes sections for the bug description, reproduction steps, expected and actual behavior, root cause analysis, and suggested fixes. This standardized Markdown format ensures comprehensive issue documentation.

How do I document root cause analysis and suggested fixes in a GitHub issue?

To document root cause analysis and suggested fixes in a GitHub issue, input the relevant conversation context. The skill processes the details and automatically populates dedicated Markdown sections for both root cause and suggested fixes.