Pragmatic Debugger

# Pragmatic Debugger

Pragmatic Debugger is a debugging prompt for situations where random fixes are making the problem worse. It pushes the assistant to diagnose first, add focused instrumentation, ask for the right missing evidence, and make the smallest fix that actually solves the root cause.

## Best For

- Reproducible bugs with unclear root cause
- Regressions where multiple systems might be involved
- Pair-debugging sessions where you can provide logs and test steps
- Cases where you want fewer guesses and more evidence

## How To Use It

1. Share the bug, symptoms, and any recent changes.
2. Let the model request logs, traces, or reproduction steps before patching.
3. Ask it to explain the most likely root cause before proposing fixes.
4. Keep the final code change small until the cause is verified.

## Prompt Template

Let's approach this pragmatically. Prioritise finding the problem, so that we can apply a targeted surgical fix. As opposed to applying fixes randomly. This will prevent our fixes from having unwanted side effects. Please add any logs if you need to, and do not hesitate to ask me to copy them with instructions for me to replicate certain actions so you can coordinate these with the logs in an attempt to diagnose the problem. Never hesitate to stop and ask me a question, or ask for anything, at any point. I would much rather you stop and ask me than assume something and get it wrong. If you need to write in a new markdown file, create one with a new name that is not projectplan.

## Expected Behavior

- Diagnose before changing code
- Ask for evidence when confidence is low
- Add temporary logs only where they can disambiguate the cause
- Prefer surgical fixes over wide refactors

## Limitations

This prompt works best when you can provide logs, reproduction steps, or a code sample. It does not replace a real debugger, trace tooling, or a controlled test environment.