skills.rest
MartinoPolo
MartinoPoloCOMMUNITY
Explore all skills by this author →
GitHub

mp-bug-report

Convert bug descriptions into GitHub issues with root-cause analysis and TDD fix plans.

1|Updated Feb 7, 2026
Search Tags:#root cause analysis#bug report#github issues#codebase investigation#labeling#issue automation#tdd planning
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-bug-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mp-bug-report
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/skills/mp-bug-report
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-bug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps investigate a reported bug, identify the root cause, and turn the findings into a durable GitHub issue with a vertical-slice TDD fix plan.

Core Features & Use Cases

  • Root-cause investigation: Extracts actual vs expected behavior and reproduction steps, then runs an issue analysis sub-agent to locate the manifestation, trace the code path, and determine the true cause.
  • TDD fix planning: Converts analysis into ordered RED-GREEN vertical slices (then REFACTOR), with tests written against public behavior contracts to stay resilient to refactors.
  • Issue creation with proper labeling: Ensures a bug label exists and creates a GitHub issue titled bug: ... that stays free of brittle details like file paths and line numbers.
  • Multi-bug support: Accepts multiple bug descriptions, splits them into separate investigations, and outputs all created issue URLs with one-line root-cause summaries.

Quick Start

Ask the AI to create bug issues by running mp-bug-report with your bug description(s) inline.

Frequently Asked Questions about mp-bug-report

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

FAQPage Schema
How do I turn bug reports into structured GitHub issues with a TDD fix plan?▼

To turn bug reports into structured GitHub issues with a TDD fix plan, provide the bug description, expected behavior, and reproduction steps. The system investigates the root cause and generates an issue with ordered RED-GREEN vertical slices.

What is root cause analysis for a bug report and how does it work?▼

Root cause analysis for a bug report extracts the actual versus expected behavior and reproduction steps, then traces the code path to locate the manifestation and determine the true cause before creating a durable GitHub issue.

Can I process multiple bug descriptions at the same time?▼

Yes, you can process multiple bug descriptions simultaneously. The system splits multiple inputs into separate investigations, performs root cause analysis for each, and outputs all created GitHub issue URLs with one-line summaries.

What is the best way to write bug issue acceptance criteria to survive refactoring?▼

The best way to write bug issue acceptance criteria that survive refactoring is using TDD vertical slices. Tests are written against public behavior contracts rather than implementation details, avoiding brittle references like file paths and line numbers.

Do I need to provide complete reproduction steps for issue automation to work?▼

No, you do not need to provide complete reproduction steps initially. The issue automation handles incomplete details by asking follow-up questions to gather the missing actual behavior, expected behavior, and reproduction steps.

Related Skills

Explore More Software Engineering Skills→
haidonglethqbhaidonglethqb

bug-report-qa

Generate structured bug reports with reproduction steps and Jira links.

Community
Intermediate
alexandrbasisalexandrbasis
12

tdd

Enforce red-green-refactor TDD cycles with vertical slice testing.

Community
Advanced
JmarquesJmarques

qa

Create GitHub issues from conversational bug reports.

Community
Advanced
RemseyMailjardRemseyMailjard

triage-issue

Investigate a reported bug and create a GitHub issue with a TDD fix plan.

Community
Intermediate