Explain code, design test cases and review a small change with prompts you can adapt to your project.
Understand inputs, outputs and assumptions before editing.
Explain this function for {{experience_level}}:
{{code}}
State its inputs, output and side effects. Walk through one concrete input. Identify assumptions and cases not covered by the snippet. Do not invent behavior from missing dependencies.Code: function first(items) { return items[0]; }. Level: beginner.
Returns the first element. Input [4, 8] returns 4. An empty array returns undefined. Passing null would fail when accessing index 0.
Before you use itRun the example in the intended environment; missing dependencies can change behavior.
Turn a behavior contract into a focused test checklist.
Propose tests for:
{{behavior}}
Relevant code:
{{code}}
Test framework: {{framework}}.
Cover one happy path, boundaries, invalid input and a regression case. Give input and expected output for each. Label uncertain expectations as contract questions. Do not claim to have executed tests.Behavior: trim a string; return an empty string for whitespace-only input; reject non-strings.
Cases: ' hi ' → 'hi'; ' ' → ''; '' → ''; 42 → rejection. Confirm the required error type before asserting it.
Before you use itCheck expected outcomes against your contract, then run actual tests.
Find concrete regressions without rewriting unrelated code.
Review this diff against the requirement:
{{requirement}}
Diff:
{{diff}}
Context:
{{context}}
Report only actionable issues introduced by the change. For each, show the triggering input, observed or inferred failure and a minimal fix. Separate verified behavior from hypotheses. Do not change files or introduce unrelated refactors.Requirement: allow zero as a valid limit. Diff changes a null check to if (!limit).
Potential regression: limit 0 is falsy and now enters the missing-value branch. Test with limit=0 and preserve an explicit null/undefined check.
Before you use itReproduce each finding. A plausible review comment is not a confirmed bug.
Copy a prompt, replace the text in double braces with your details, then adjust the first draft.
A small snippet is easier to review when the assistant knows what it must do. Supply the relevant runtime and test framework, but never paste credentials or private data you are not allowed to share.
Use the output to guide your investigation. Execute tests locally and review the diff before merging a change.
Understand inputs, outputs and assumptions before editing.
Explain this function for {{experience_level}}:
{{code}}
State its inputs, output and side effects. Walk through one concrete input. Identify assumptions and cases not covered by the snippet. Do not invent behavior from missing dependencies.Code: function first(items) { return items[0]; }. Level: beginner.
Returns the first element. Input [4, 8] returns 4. An empty array returns undefined. Passing null would fail when accessing index 0.