DevOps Engineer · Runs on ChatGPT GPT-5.5 · 5 cr./message

AI assistant: builds, deploys and what to do when it breaks

CI/CD, containers, environments and incident triage: ordered hypotheses instead of random advice.

What DevOps Engineer returns

The shape of the answer is fixed in advance: does the build pass, does the image arrive, does the process start, are variables and permissions present, is the network reachable. Two conversations about the same task therefore end in the same form: the answer can be compared with the previous one and passed on without asking for a rewrite.

“Work through an incident by layers in a fixed order: does the build pass, does the image arrive, does the process start, are variables and permissions present, is the network reachable, are resources sufficient.”

What DevOps Engineer will not do

The role has 6 rules, 2 prohibitions among them outright. We quote them as written rather than paraphrase: promising “it can do anything” is cheaper, but then people meet the limit only after paying for a message. Here it is visible beforehand, and a neighbouring role can be picked straight away.

“Never invent flags, config keys, variable names or version behavior; when unsure, say it must be verified against that version's documentation.”

“Never invent secrets, keys or tokens in examples and never ask for them in chat — show how to pass them through environment variables and a secrets store.”

How DevOps Engineer runs the review

The rules describe the role as “practicing DevOps engineer”. Below is how it holds the review, in the same words it is given before your first message — and manner is exactly what separates one companion from another.

“First establish the stack, platform, deployment method, versions and what changed right before the failure.”

“Pair every hypothesis with a check — a command or a place in the logs — rather than an assertion.”

What a message to the “Builds, deploys and what to do when it breaks” role costs

You are charged per message sent, not per month of access: a role needed once a quarter costs nothing in between, and it needs no line of its own in the budget.

5 credits per messageThe price is the same for a short and a long message: what counts is the send, not the length.No subscription feeTen messages a month cost the price of ten messages: you pay for what happened, not for a plan.

What DevOps Engineer flags for checking

The danger is not a gap in knowledge but a confident tone over a guess: people act on such answers, and the cost of the mistake lands on the person, not the program. So the rules say separately what to flag, what to warn about and when to ask for a source.

“Always flag destructive operations (deleting volumes, force pushes, migrations, restarting production), state what they break irreversibly and offer a way to verify on a copy first.”

Three questions DevOps Engineer offers first

A click opens the chat with the message already typed. These are not our examples but the role’s own suggestion: the same three lines stand in the empty conversation window.

The deploy failed — help me triage

Design a pipeline for my stack

Why does the container not start?

Questions about this assistant

Quick answers

Yes: the send is charged, not the quality of the answer — 5 credits per message. That is exactly why the role starts with clarifying questions: one precise question costs less than three vague ones.

ChatGPT GPT-5.5. A role is character and rules, but a model executes them, so the model is fixed for this assistant: a weaker one would turn analysis into paraphrase, an unnecessarily strong one into overpaying. You can switch models inside the chat.

Both roles sit on the “Code and technology” shelf but answer by different rules: the rules of DevOps Engineer are quoted in full on this page, and those of “Prompt Engineer” on its own. The full shelf is listed at the end of this page.

Yes, the conversation stays in your account history: you can return to it, continue from the same point or start over.

An assistant is AI, not a person: it helps with a task but does not replace a doctor, therapist, lawyer or other qualified professional. Verify important decisions and facts against a primary source.

How DevOps Engineer differs from a plain chat

In a plain chat the framing is on you: the order of questions, the limits, the requirements for the answer — from scratch in every new window. Here it is already written: 6 rules, 2 prohibitions of them, all quoted on this page. You never have to restate them.

✓ Rules: 6, prohibitions: 2
✓ Catalogue shelf: Code and technology
✓ A program answers, not a person: it replaces no doctor, lawyer or therapist