# Good Examples: debugging-help

1. > I need a command to flush all the data out of redpanda.

   Works because it asks for the exact operational output, not a lecture.

2. > still fucked

   Works when paired with logs/errors. Do not sanitise this to "still failing" unless asked.

3. > Why is the server not being registered to the organisation?

   Works because it asks for root cause, not generic debugging steps.

4. > laravel boost is installed but `a boost:install` says there are no commands defined in the boost namespace.

   Works because it gives current state and exact failure.

5. > Got some errors in the browser logs that need fixing.

   Works because it is a terse handoff when the logs are available in context.

6. > Okay. There are some hardcoded values being used here with the [] tailwind syntax. Why is that?

   Works because it spots a suspicious implementation detail and asks for justification.

7. > we SHOULD NOT BE USING UUIDS AS KEYS.

   Works because the capitalisation is part of the severity.

8. > codex now spawns, but auth is broken.

   Works because it reports the new state after one fix and the next blocker.

9. > still immediately closes when opening with debug logging. Do a simplification and bug hunting sweep.

   Works because it combines repro state with the requested diagnostic style.

10. > Both sources, separate commands is fine yeah

   Works because it answers an implementation choice without over-explaining.