pm-bug-reporting

Standardize bug reporting for Claude MPM plugins with templates and repository routing.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-bug-reporting-bobmatnyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-bug-reporting
Source: https://github.com/bobmatnyc/claude-mpm-marketplace/tree/main/plugins/claude-mpm/skills/mpm-bug-reporting
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-bug-reporting-bobmatnyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and streamlines bug reporting for Claude MPM plugins, ensuring issues are created consistently, triaged correctly, and routed to the right repos.

Core Features & Use Cases

  • Standardized bug templates for core MPM, agents, and skills to capture what happened, expected behavior, steps to reproduce, and impact.
  • Automatic routing guidance to the correct GitHub repository (core MPM, agents, or skills) and escalation pathways when ticketing is unavailable.
  • Guidance for using GitHub CLI (gh) and ticketing workflows to create and track issues with proper labels and structure.
  • Use Case: When a research agent misbehaves, a user can generate a ticket that details the error, repository, and context, enabling fast remediation.

Quick Start

Create a bug report using the ticketing workflow to file a GitHub issue in the appropriate repository with the template and labels.

Frequently Asked Questions about pm-bug-reporting

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

FAQPage Schema
How do I report a bug in a Claude MPM plugin?

Standardized bug reporting for Claude MPM plugins requires routing issues to the correct GitHub repository with consistent templates, specific labels, and structured bodies. It covers PM bugs, agent issues, and skill-content discrepancies across the ecosystem.

How does bug routing work for MPM agent issues?

Bug routing directs issues to the correct GitHub repository—core MPM, agents, or skills—based on the error source. It enforces consistent templates with structured bodies and specific labels for proper triage and fast remediation.

Can I use the gh CLI to create GitHub issues for MPM bugs?

Yes, the bug reporting workflow supports using GitHub CLI (gh) and ticketing workflows to create and track issues. It provides guidance on applying proper labels and structured templates when filing tickets via gh CLI.

What is the escalation pathway when GitHub ticketing is unavailable?

When GitHub ticketing is unavailable, the bug reporting workflow provides specific escalation pathways for MPM plugin issues. These pathways ensure issues are still documented and routed for fast remediation across the ecosystem.

What should a GitHub issue template include for MPM bug reporting?

A standardized MPM bug report template captures what happened, expected behavior, steps to reproduce, and impact. It requires specific labels and structured bodies to ensure issue creation quality across core MPM, agents, and skills.