CodingClaude ChatGPT10d ago2 blanks

Blameless postmortem from an incident timeline

Daniel Okafor@danielokafor

Remix

Fill in the blanks

0 of 2 filled

Time zone

Paste timeline

The prompt

Turn this incident timeline into a blameless postmortem.

Summary: what users saw, for how long, how many were affected
Timeline: in time zone, one line per event
Root cause: technical, never "human error"
What went well, what didn't
Action items: owner, due date, and whether each one prevents or detects

If the timeline has gaps longer than 15 minutes, point them out.

Timeline:
paste timeline

Open inChatGPT Claude Perplexity

Fill in the blanks above to copy or open the prompt with your details in it.

690 uses301 saves170 likes4 remixes (0 public)Published 26 Sept 2026

A use is a copy, a fill-in copy, an insert or an open in an AI chat, counted once per person per day. Authors' own uses don't count.

More like this

Coding

Stack trace to root cause in three sentences

Read this stack trace from service name (language / framework). In three sentences: what failed, the most likely root cause, and the first thing I should check. Then list up to three other possible causes, ranked, each with the log line or metric that would confirm it. If the trace is cut off or ambiguous, say what extra information you need instead of guessing. paste stack trace

Arjun Mehta

Example output: a code review of a small diff, with two findings pinned to lines, concrete fixes, and the verdict “Ship after fixes”.

CodingStaff pick

Code review like a careful senior

Arjun Mehta

Coding

A regex, with tests that prove it

Write a regex in language that matches what it should match and does not match what it should not. Then give 8 test strings: 4 that should match and 4 that shouldn't, including edge cases like empty strings and Unicode. Explain each part of the pattern in a table. If a regex is the wrong tool here, say so and show the alternative.

Arjun Mehta

Coding

Unit tests for a function I paste

Write test framework tests for the function below. Cover the happy path, the boundaries, invalid input, and one property that should always hold. Use test names that read as sentences. Don't mock what you don't own. If the function is hard to test, suggest the smallest refactor that would help. paste function

Arjun Mehta

Coding

Explain this module to a new teammate

Explain this language module to a new teammate who knows the language but not our codebase. Start with what it's for in one sentence, then the main flow, then the two things most likely to trip them up. Point to functions by name. Finish with a Mermaid sequence diagram of the call flow. paste code

Daniel Okafor

Display · responsive