Auto Bug Reporter
Automatically file GitHub issues when you encounter errors, crashes, or unexpected behavior in claude-mpm during a session.
Trigger Conditions
File an issue automatically when you encounter ANY of the following:
- Import errors in claude-mpm modules (e.g.,
ModuleNotFoundError, ImportError from claude-mpm source paths)
- Hook errors — stop hook, start hook, or prompt hook failures
- Agent deployment failures — agent fails to start, crashes mid-task, or returns unexpected errors
- Skill deployment failures — skill fails to load, parse, or execute
- MCP tool errors from claude-mpm tools (e.g.,
mcp-ticketer, mpm-messaging, mcp-vector-search when used within claude-mpm context)
- Test failures in claude-mpm's own test suite (not user project tests)
- CLI errors from
claude-mpm commands (e.g., claude-mpm init, claude-mpm run, claude-mpm doctor)
- Configuration errors — missing config, invalid YAML, malformed
.claude/settings.json
- Orchestration errors — PM fails to delegate, agent routing breaks
Do NOT File Issues For
- User project errors unrelated to claude-mpm internals
- Rate limit errors from Anthropic API (HTTP 429)
- Network connectivity issues (DNS failures, timeouts)
- Pyright or mypy diagnostics in user code (not claude-mpm source)
- Pre-existing known issues already filed (search first)
- Errors from user-written hooks or custom agents not part of claude-mpm
How to File
Use the mcp__github__create_issue tool:
- Owner:
bobmatnyc
- Repo:
claude-mpm
- Labels:
["bug", "auto-reported"]
- Title format:
auto: <brief description of error>
Issue Body Template
## Auto-Reported Bug
**Encountered during**: <what the user was doing when the error occurred>
**Error**: <exact error message or traceback>
**File**: <file path and line number if known>
**Version**: <claude-mpm version if known — run `claude-mpm --version` or check pyproject.toml>
## Reproduction
<steps or context that led to the error>
## Severity
- [ ] Blocking (prevents core functionality)
- [ ] Degraded (workaround exists)
- [ ] Cosmetic (no functional impact)
_Filed automatically by claude-mpm auto-bug-reporter_
Step-by-Step Procedure
Detect the error — identify it matches a trigger condition above.
Search for duplicates first using mcp__github__search_issues:
repo:bobmatnyc/claude-mpm is:issue <key error terms>
If a matching open issue already exists, skip filing and note the existing issue number.
Gather context:
- Exact error message or stack trace
- What the user was attempting when the error occurred
- File path and line number if visible
- claude-mpm version (check
pyproject.toml or uv run claude-mpm --version)
File the issue using mcp__github__create_issue with owner bobmatnyc, repo claude-mpm, the title and body from the template above, and labels ["bug", "auto-reported"].
Tell the user immediately after filing:
Filed auto-bug-report: #<issue_number> — <title>
Continue the user's task — do not stop or wait. The issue is filed; move on.
Rate Limiting
- Do not file duplicate issues — always search existing issues first.
- Maximum 3 auto-filed issues per session to avoid noise.
- If you have already filed 3 issues in the current session, log the error to the user verbally but do not file another issue.
Severity Guidance
| Error Type |
Severity |
| Agent or hook completely non-functional |
Blocking |
| CLI command fails with traceback |
Blocking |
| MCP tool errors breaking workflow |
Blocking |
| Config error with a manual workaround |
Degraded |
| Incorrect output, wrong behavior |
Degraded |
| Minor display or formatting glitch |
Cosmetic |
Example Filed Issue
Title: auto: ModuleNotFoundError for claude_mpm.hooks.stop_hook
Body:
## Auto-Reported Bug
**Encountered during**: Running `claude-mpm run` with a custom stop hook configured
**Error**: `ModuleNotFoundError: No module named 'claude_mpm.hooks.stop_hook'`
**File**: `src/claude_mpm/hooks/stop_hook.py` (missing)
**Version**: 6.2.5
## Reproduction
1. Configure a stop hook in `.claude/settings.json`
2. Run `claude-mpm run`
3. At session end, hook dispatch fails with ModuleNotFoundError
## Severity
- [x] Blocking (prevents core functionality)
_Filed automatically by claude-mpm auto-bug-reporter_
Related Skills
mpm-bug-reporting — Manual PM-driven bug reporting with routing to multiple repos
mpm-verification-protocols — QA evidence standards
mpm-doctor — Diagnosing claude-mpm environment issues
1---2name: auto-bug-reporter3description: Automatically file GitHub issues when claude-mpm errors are encountered during a session4---56# Auto Bug Reporter78Automatically file GitHub issues when you encounter errors, crashes, or unexpected behavior in claude-mpm during a session.910## Trigger Conditions1112File an issue automatically when you encounter ANY of the following:1314- **Import errors** in claude-mpm modules (e.g., `ModuleNotFoundError`, `ImportError` from claude-mpm source paths)15- **Hook errors** — stop hook, start hook, or prompt hook failures16- **Agent deployment failures** — agent fails to start, crashes mid-task, or returns unexpected errors17- **Skill deployment failures** — skill fails to load, parse, or execute18- **MCP tool errors** from claude-mpm tools (e.g., `mcp-ticketer`, `mpm-messaging`, `mcp-vector-search` when used within claude-mpm context)19- **Test failures** in claude-mpm's own test suite (not user project tests)20- **CLI errors** from `claude-mpm` commands (e.g., `claude-mpm init`, `claude-mpm run`, `claude-mpm doctor`)21- **Configuration errors** — missing config, invalid YAML, malformed `.claude/settings.json`22- **Orchestration errors** — PM fails to delegate, agent routing breaks2324## Do NOT File Issues For2526- User project errors unrelated to claude-mpm internals27- Rate limit errors from Anthropic API (HTTP 429)28- Network connectivity issues (DNS failures, timeouts)29- Pyright or mypy diagnostics in user code (not claude-mpm source)30- Pre-existing known issues already filed (search first)31- Errors from user-written hooks or custom agents not part of claude-mpm3233## How to File3435Use the `mcp__github__create_issue` tool:3637- **Owner**: `bobmatnyc`38- **Repo**: `claude-mpm`39- **Labels**: `["bug", "auto-reported"]`40- **Title format**: `auto: <brief description of error>`4142### Issue Body Template4344```markdown45## Auto-Reported Bug4647**Encountered during**: <what the user was doing when the error occurred>48**Error**: <exact error message or traceback>49**File**: <file path and line number if known>50**Version**: <claude-mpm version if known — run `claude-mpm --version` or check pyproject.toml>5152## Reproduction5354<steps or context that led to the error>5556## Severity5758- [ ] Blocking (prevents core functionality)59- [ ] Degraded (workaround exists)60- [ ] Cosmetic (no functional impact)6162_Filed automatically by claude-mpm auto-bug-reporter_63```6465## Step-by-Step Procedure66671. **Detect the error** — identify it matches a trigger condition above.68692. **Search for duplicates first** using `mcp__github__search_issues`:70 ```71 repo:bobmatnyc/claude-mpm is:issue <key error terms>72 ```73 If a matching open issue already exists, skip filing and note the existing issue number.74753. **Gather context**:76 - Exact error message or stack trace77 - What the user was attempting when the error occurred78 - File path and line number if visible79 - claude-mpm version (check `pyproject.toml` or `uv run claude-mpm --version`)80814. **File the issue** using `mcp__github__create_issue` with owner `bobmatnyc`, repo `claude-mpm`, the title and body from the template above, and labels `["bug", "auto-reported"]`.82835. **Tell the user** immediately after filing:84 ```85 Filed auto-bug-report: #<issue_number> — <title>86 ```87886. **Continue the user's task** — do not stop or wait. The issue is filed; move on.8990## Rate Limiting9192- Do not file duplicate issues — always search existing issues first.93- Maximum **3 auto-filed issues per session** to avoid noise.94- If you have already filed 3 issues in the current session, log the error to the user verbally but do not file another issue.9596## Severity Guidance9798| Error Type | Severity |99|---|---|100| Agent or hook completely non-functional | Blocking |101| CLI command fails with traceback | Blocking |102| MCP tool errors breaking workflow | Blocking |103| Config error with a manual workaround | Degraded |104| Incorrect output, wrong behavior | Degraded |105| Minor display or formatting glitch | Cosmetic |106107## Example Filed Issue108109**Title**: `auto: ModuleNotFoundError for claude_mpm.hooks.stop_hook`110111**Body**:112```markdown113## Auto-Reported Bug114115**Encountered during**: Running `claude-mpm run` with a custom stop hook configured116**Error**: `ModuleNotFoundError: No module named 'claude_mpm.hooks.stop_hook'`117**File**: `src/claude_mpm/hooks/stop_hook.py` (missing)118**Version**: 6.2.5119120## Reproduction1211221. Configure a stop hook in `.claude/settings.json`1232. Run `claude-mpm run`1243. At session end, hook dispatch fails with ModuleNotFoundError125126## Severity127128- [x] Blocking (prevents core functionality)129130_Filed automatically by claude-mpm auto-bug-reporter_131```132133## Related Skills134135- `mpm-bug-reporting` — Manual PM-driven bug reporting with routing to multiple repos136- `mpm-verification-protocols` — QA evidence standards137- `mpm-doctor` — Diagnosing claude-mpm environment issues