Review before you change
Get a structured review of a code change
Provide code, expected behaviour, and reproduction details to receive prioritised findings and checks.
A fictional example was checked by the author against the acceptance criteria. No model was run.
Your three-step path
Start here, then build on it
Open each official resource when you are ready.
- 01Free resource
Review code and propose tests
Find likely defects and propose checks without running code or changing services.
Official resource · Review code and propose tests · English
Open resource - 02Free resource
Plan an AI workflow
Map inputs, tools, permissions, failure handling, and a dry-run for an automation task.
Official resource · Plan an AI agent workflow · English
Open resource - 03Free resource
Research with evidence
Compare supplied technical sources while keeping dates and claims traceable.
Official resource · Research with evidence · English
Open resource
The result
What you will prepare
Leave with actionable review findings, a minimal proposed fix, and a way to verify it.
- Prioritised findings with code locations
- A minimal proposed correction
- Regression scenarios and acceptance checks
Before you begin
Have these details ready
- Relevant code with secrets removed
- Language, framework, and versions
- Expected behaviour and a reproducible example or test
Share only information needed for the task. Remove passwords, secrets, and personal details that are not required.
Illustration
A fictional worked example
Example checked. A fictional example was checked against the path checklist. No model was run.
A fictional developer shares a small date-formatting function and an example where an empty value becomes an invalid date. The review proposes a guard and test cases for empty, valid, and malformed inputs; no code is executed. The finding matches that empty-value example. The note refers to the function the developer supplied, without a guessed line number. The checks cover empty, valid, and malformed inputs. No secret or customer data is in the example.
Your final pass
Review before you use it
- Do findings match the expected behaviour and supplied code?
- Are line references accurate?
- Do tests cover normal, boundary, and failure cases?
- Are secrets, tokens, and customer data excluded?