From pact
Logs bug investigations using PACT protocol: creates YAML files tracking symptoms, attempts, root causes, fixes, and reusable solutions in .claude/bugs/. Useful for systematic debugging.
npx claudepluginhub jonathanmr22/pact --plugin pactThis skill uses the workspace's default tool permissions.
Create or update a PACT bug tracking file. Follow this protocol:
Executes hypothesis-driven debugging workflow: triage and reproduce bugs, investigate with evidence, analyze root causes, fix and verify, then report. For 'fix this bug' or debug requests.
Runs structured bug investigation: reproduce issue, trace root cause, test hypotheses, apply TDD fixes via sub-agent, escalate after failures. Use /cdebug when stuck on bugs.
Fixes bugs via root cause diagnosis with debugger/gap-analyzer, requirements.md generation, /execute delegation, 3-retry circuit breaker, and QA.
Share bugs, ideas, or general feedback.
Create or update a PACT bug tracking file. Follow this protocol:
Step 1: Check existing solutions first.
Read .claude/bugs/_SOLUTIONS.yaml and search for matching tags. If a previous session already solved this class of bug, report the existing solution instead of re-investigating.
Step 2: Create the bug file.
If no existing solution matches, create .claude/bugs/{system}/{system}-NNN.yaml with:
id, title, status: investigating, severity, system, tagssymptom — what was observedexpected — what should happeninvestigation — log every attempt in real time (attempt number, what was tried, result)Step 3: Update as you investigate. Add each attempt to the investigation log as you try things. Failed attempts are as valuable as successes — they prevent the next session from wasting hours on dead ends.
Step 4: When fixed, complete the record.
Update status: fixed, add root_cause, fix, files_changed, and prevention.
Step 5: Graduate reusable solutions.
If the fix applies to a class of bugs (not just this specific instance), add an entry to .claude/bugs/_SOLUTIONS.yaml with tags for future matching.