Claude Debugging Prompt for DevOps Engineers
You get a short list of likely causes ranked by probability, plus the exact checks to run that confirm or rule out each one. This prompt is tuned for devops engineers working in Claude: it carries your role context, and the steps below cover what changes in Claude. Check IAM permissions, open ports, secrets handling and destructive commands in any generated config or script before it touches a real environment.
Help me debug a problem. I want to find the cause, not just patch the symptom. ## Symptom [what you see, how often, and since when] ## Environment [language, framework, versions, OS, local or production] ## Relevant code and logs [paste the code involved and any log output or stack trace] ## What changed recently [deploys, dependency updates, config changes, or "nothing I know of"] ## What I have already checked [and what each check showed] ## Instructions - List the likely causes, most probable first, and say why each fits the evidence. - For each cause, give one specific check (a log line to add, a command to run, a value to print) that confirms or rules it out. - Do not propose a fix until we have narrowed it down, unless the cause is obvious. ## Output format A numbered list: cause, why it fits, how to check it. Then one line on which check to run first. About my work - Platform and tools: [e.g. AWS, Terraform 1.8, GitHub Actions, Kubernetes 1.30] - Environment this affects: [e.g. staging only, production with 3 regions] - Constraints: [e.g. no downtime, must stay within the current IAM roles] Context - Reference material: [paste it below, or attach the file]
How to use this prompt
- 1
Open Claude
Start a new chat in Claude and paste the prompt.
- 2
Give it context
Attach the documents, code or data the prompt refers to, or paste them below the prompt.
- 3
Review and iterate
Reply in the same chat to refine. Point to the exact part you want changed.
- 4
Save what you repeat
If you use this prompt often for one body of work, set it up in a Claude Project with the instructions and reference files saved.
Working in Claude
- •Claude handles long documents well, so paste the full source text rather than a summary when accuracy matters.
- •Longer pieces of writing or code may open in a side panel (an artifact) that you can edit and ask Claude to revise.
- •Clear structure helps: separate instructions from the material with headings or tags such as <document>.
Worked example
What you give it
Symptom: add_tag returns tags from earlier calls. Calling add_tag("a") then add_tag("b") gives ["a", "b"] on the second call instead of ["b"].
Environment: Python 3.11, local script.
def add_tag(tag, tags=[]):
tags.append(tag)
return tags
What changed: nothing, it has always done this.What a good answer looks like (shortened)
1. Mutable default argument (very likely). The list [] is created once, when the function is defined, and every call without a tags argument reuses that same list.
Check: print(id(tags)) inside the function. If the id is the same on every call, this is the cause.
2. A caller is passing the same list in each time (less likely, since the calls you showed pass only one argument).
Check: search for calls to add_tag that pass a second argument.
Run check 1 first. If confirmed, the fix is:
def add_tag(tag, tags=None):
if tags is None:
tags = []
tags.append(tag)
return tagsTips for better results
- •Always say which environment the change targets and ask for a plan or dry-run command before the apply step. It keeps a test idea from turning into a production change.
- •Write "What I have already checked" with results, not just actions. "Restarted the server, error still happens on the first request" rules out more than "restarted the server."
- •Longer pieces of writing or code may open in a side panel (an artifact) that you can edit and ask Claude to revise.
- •Avoid this: Leaving out what changed recently, which is often the fastest clue to an issue that started suddenly.
Check before you use it: Check IAM permissions, open ports, secrets handling and destructive commands in any generated config or script before it touches a real environment.
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.
Variations
Intermittent bug
Add this line to Symptom: It only happens [e.g. 1 in 20 requests, under load, after midnight UTC]. Focus on timing, concurrency and caching causes.
Production only
Add this line to Instructions: I cannot attach a debugger. Suggest only checks that work through logs, metrics or config.
Add logging
Change Output format to: The exact log statements to add, where to put them, and what each output would tell us.
Save it as a Retext snippet
Retext is a free text expander for Mac. Save this prompt once, then type ;debug in any app (ChatGPT, Claude, your editor, a browser tab) and the full prompt is pasted in.
- Click Add to Retext. The prompt installs as a snippet with the trigger ;debug.
- Change the trigger in Retext if you prefer a different one.
- Type the trigger wherever you want the prompt, then fill in the brackets.
Frequently asked questions
Is it safe to use AI for Terraform or Kubernetes configs?
It is useful for drafts and reviews, but configs can contain subtle mistakes like overly broad permissions. Review every change with a plan or diff and test in a non-production environment first.
What is the difference between debugging and bug fixing prompts?
A debugging prompt is for when you do not know the cause yet, so it asks for hypotheses and checks. A bug fix prompt is for when you can reproduce the problem and want a patch.
Should I use a Claude Project for this prompt?
If you run it often against the same reference material, yes. Save the prompt as the project's instructions and upload the files once.
How do I reuse this prompt without copying it every time?
Click Add to Retext to save it as a snippet. Then type ;debug in any Mac app, including your AI tool, and the full prompt is pasted in.
Related Templates
Get the free prompt pack
Our best coding prompts in one Markdown file, delivered by email. The templates here stay free either way — the pack just saves you the copying.