MartinoPolo/mp-bug-report
skills/mp-bug-report/SKILL.md
Investigate bug root cause, design TDD fix plan, create GitHub issue labeled bug. Accepts multiple bugs. Use when: "report bug", "bug report", "something is broken", "investigate bug"
$ install --global
skillsauthnpx skillsauth add MartinoPolo/mpx-claude-code mp-bug-reportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 5:51 AM128.6s1 file scanned
SKILL.md
- name:
- mp-bug-report
- description:
- Investigate bug root cause, design TDD fix plan, create GitHub issue labeled bug. Accepts multiple bugs. Use when: "report bug", "bug report", "something is broken", "investigate bug"
- argument-hint:
- bug description(s) — inline text or multiple descriptions separated by newlines
- disable-model-invocation:
- true
- allowed-tools:
- Read, Glob, Grep, Bash(gh *), Bash(git *), AskUserQuestion, Agent
- author:
- MartinoPolo
- version:
- 0.3
- category:
- issue-management
Bug Report
Investigate bug root cause, design TDD fix plan, create GitHub issue. $ARGUMENTS
Input Resolution
- If
$ARGUMENTSprovided: parse as bug description(s). Split on double newlines (\n\n) for multiple bugs — each block becomes a separate investigation. - If no arguments: ask user to describe the bug(s).
- Single bug = single investigation. Multiple bugs = parallel investigations.
Process (per bug)
Step 1: Capture Problem
Parse bug description for:
- Actual behavior — what happens now
- Expected behavior — what should happen
- Reproduction steps — how to trigger it
If critical info is missing (can't investigate without it), ask questions. Then move to investigation promptly.
Step 2: Investigate
Spawn mp-issue-analyzer sub-agent:
Explore this codebase to investigate a bug.
Bug: [parsed description]
Your tasks:
- Find where the bug manifests in the codebase
- Trace the code path involved
- Identify the root cause (not just the symptom)
- Find related code, patterns, and existing tests
Return your full analysis including root cause, affected modules, and code path description.
For multiple bugs: spawn multiple mp-issue-analyzer sub-agents in parallel.
Step 3: Design TDD Fix Plan
Based on investigation results, design ordered RED-GREEN cycles:
- Each cycle is a vertical slice: RED (one test capturing broken/missing behavior) then GREEN (minimal code change to pass)
- Tests verify behavior through public interfaces, not implementation details
- Each test should survive internal refactors
- Final step: REFACTOR for cleanup after all cycles pass
Step 4: Create GitHub Issue
Ensure bug label exists:
gh label create bug --description "Bug report" --color D73A4A --force
Title format: bug: [concise description]
Create issue:
gh issue create --title "bug: description" --label "bug,area-label" --body "$(cat <<'EOF'
## Problem
**Actual behavior:** [what happens]
**Expected behavior:** [what should happen]
**How to reproduce:**
1. [step 1]
2. [step 2]
## Root Cause Analysis
[Code path description — why it fails, contributing factors]
[Describe modules, behaviors, and contracts — NO file paths or line numbers]
## TDD Fix Plan
1. **RED:** [test description — what behavior to verify]
**GREEN:** [minimal change to make test pass]
2. **RED:** [next test]
**GREEN:** [next change]
3. **REFACTOR:** [cleanup after all tests pass]
## Acceptance Criteria
- [ ] [criterion 1]
- [ ] [criterion 2]
EOF
)"
Add labels: bug + any area labels detected from codebase exploration.
Step 5: Report
- Print issue URL and one-line root cause summary per bug
- Multiple bugs: list all issue URLs with brief summary each
Rules
- Issue body must be durable — no file paths, line numbers, or implementation details that break after refactors
- Describe modules, behaviors, and contracts instead
- Use project's domain language (check
.mpx/CONTEXT.md§ Domain Language) - Each RED-GREEN cycle is a vertical slice — NOT horizontal
- Keep investigation thorough but issue body concise
Related Skills
MartinoPolo/mp-skill-audit
development
VerifiedTrustedCommunity
Audit all active skills for consistency, convention drift, and common issues. Auto-fixes where possible, reports remaining issues. Use when: "audit skills", "skill audit", "check skills", "lint skills"
1SKILL.mdUpdated May 19, 2026
MartinoPolo/mp-ship
testing
VerifiedTrustedCommunity
Ship finished work: sync base, commit, push, PR, wait for CI green, merge. Use when: "ship it", "ship and merge", "ship this"
1SKILL.mdUpdated May 19, 2026
MartinoPolo/mp-harvest-decisions
development
VerifiedTrustedCommunity
Scan recent Claude Code sessions for grilling/design discussions, extract decisions, and update CONTEXT.md + DECISIONS.md. Use when: "harvest decisions", "extract decisions from sessions", "update docs from sessions", "sync decisions"
1SKILL.mdUpdated May 19, 2026
MartinoPolo/mp-consolidate-context
tools
VerifiedTrustedCommunity
Consolidate CONTEXT.md: remove duplicates, outdated items, tighten language. Use when: "consolidate context", "clean up context", "simplify context", "consolidate requirements"
1SKILL.mdUpdated May 19, 2026