Stats
Actions
Tags
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pact:pact-bugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create or update a PACT bug tracking file. Follow this protocol:
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.
npx claudepluginhub jonathanmr22/pact --plugin pactRoot cause based one-shot bug fix. Runs a full investigation pipeline: debugger diagnosis, gap analysis, requirements generation, execution, and verification. Includes QA suggestions after successful fix.
Orchestrates persistent, hypothesis-driven debugging sessions across conversations, delegating analysis to subagents and tracking in debug files.
Investigates bugs iteratively via guided conversation with diagnostic analysis, producing fixes or structured specs for Arness pipeline. Triggers on bug reports or debug requests.