pm-bug-reporting

Standardizes GitHub issue creation for reporting MPM framework, agent, and skill bugs.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/MacPhobos/research-mind --skill pm-bug-reporting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-bug-reporting
Source: https://github.com/MacPhobos/research-mind/tree/main/.claude/skills/mpm-bug-reporting
Command: npx skills add https://github.com/MacPhobos/research-mind --skill pm-bug-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized protocol for reporting bugs encountered within the MPM framework, its agents, or skills, ensuring clear, actionable GitHub issues are created efficiently.

Core Features & Use Cases

  • Standardized Bug Reporting: Ensures all necessary information (title, labels, body, context) is included for effective issue tracking.
  • Repository Routing: Directs bugs to the correct GitHub repository (core MPM, agents, or skills).
  • Agent Delegation: Facilitates delegation to a ticketing agent for automated issue creation.
  • Use Case: When an agent behaves unexpectedly, this skill guides the process to create a detailed GitHub issue in the claude-mpm-agents repository, complete with reproduction steps and relevant labels.

Quick Start

Delegate to the ticketing agent to create a GitHub issue for a core MPM bug with the title "PM fails to load configuration on startup".

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 to GitHub for MPM framework errors?

To report an MPM framework bug to GitHub, you standardize the issue creation process by routing the bug to the correct repository, applying required labels, and filling out a detailed body template with reproduction steps.

What is the best way to track agent errors in a ticketing system?

Tracking agent errors involves delegating the bug report to a ticketing agent, which creates a detailed GitHub issue complete with reproduction steps and relevant labels in the appropriate agents repository.

How do I structure a GitHub issue for skill errors?

Structuring a GitHub issue for skill errors requires using a standardized protocol that defines repository routing, specifies required labels, and provides a detailed body template with examples for skill-specific bugs.

Can I use a ticketing agent to automate GitHub issue creation?

Yes, you can delegate the bug reporting process to a ticketing agent to automate GitHub issue creation, ensuring all necessary context, titles, and labels are included for effective issue tracking.

When do I need to escalate a bug in the MPM workflow?

Escalating a bug in the MPM workflow is needed when standard issue creation is insufficient, utilizing defined escalation paths and PM enforcement guidelines to ensure the core MPM, agent, or skill bug is resolved.