Prompts to steal. 32 jobs, one paste each.
Every prompt here runs against your own stack: your clouds, your telemetry, your deploys, your code. Paste one into a console thread, into Slack, or into your coding agent over MCP.
Impact analysis
Catch the bad change before it merges.
“Review PR #241 against production: what does it deploy to, and what breaks if it merges?” 
“If checkout-api goes down, what goes down with it? Walk the graph and rank by traffic.” 
“We're renaming the orders table tonight. Which services, queries, and crons touch it?” 
“List every deploy since Friday and flag the ones whose metrics moved afterwards.” 
“Write release notes for this week's deploys, including what regressed and what got fixed.” “Which services are closest to their limits: connection pools, queues, compute?” Incident response
Triage to root cause while you're still waking up. 
“Triage everything that fired overnight: what was real, what was noise, and what's still open?” “P99 on checkout-api doubled at 14:10. Find the cause and show the evidence.” “Write the postmortem for yesterday's incident: timeline, root cause, and the follow-ups.” “We're seeing 500s on api.example.com. Start an investigation and post findings to #incidents.” “Did anything deploy or change config in the last two hours that could explain this latency?” “Summarise the open incident for the exec channel: impact, cause so far, next steps.” “The incident is resolved. Draft the permanent fix and link the evidence.” “Errors started around Tuesday. Which release introduced them?” “Group last month's pages into distinct issues. How many were the same thing twice?” “Go through our alert rules: which ones fire the most, and which were ever real?” 
“Find things that look wrong but never alerted: error spikes, dead crons, growing queues.” “Map our AWS account: what's running, what depends on what, and what's critical?” “Find the risky configuration: public buckets, missing alarms, single points of failure.” “List every scheduled job across our clouds and when each one last succeeded.” 
“Which critical services have no logs or traces? Show the gaps and write the fixes.” 
“Go through our dashboards and tell me what's drifting from normal this week.” “Write the query for checkout error rate by region over 24 hours, and save it as a check.” “Which routes swallow errors or log nothing? Show the gaps and the fixes.” “Summarise what our telemetry says about last week: regressions, improvements, anything odd.” “We're deploying checkout-api at 5pm. Watch the metrics after and flag anything that moves.” “I'm new here. Walk me through the architecture: the critical path, the data stores, what talks to what.” “payments-v2 ships next week. What instrumentation should it have before launch? Draft it.” Ticket resolution
Turns a bug report into a fix, with the digging done. “Users report intermittent timeouts on search. Find the cause and draft the fix.” “Can you confirm the bug in ticket #513 from the logs, and which release introduced it?” “What should support tell customers about yesterday's checkout errors? Keep it accurate.” “This flaky 502 has been in the backlog for a month. Find the actual cause.”