Search
in:coding
6 public prompts in Coding
Prompts
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 Mehta2,240 uses
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 Mehta720 uses
Turn this incident timeline into a blameless postmortem.
1. Summary: what users saw, for how long, how many were affected
2. Timeline: in time zone, one line per event
3. Root cause: technical, never "human error"
4. What went well, what didn't
5. 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
Daniel Okafor690 uses
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 Okafor510 uses
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 Mehta990 uses