Free Tool · Release Review
Review change risk before calling it release-ready
Identify direct impact, downstream effects, uncertainty, and the engineering follow-up needed for a PR, story, requirement, or code change. Workspace connects this analysis to real tests and run evidence.
Continue with project evidence →Change Input
Describe the software change
Start with the required fields. Additional context improves evidence confidence and result specificity.
Required
A real change with risk in it, so you can see what a review looks like before writing your own.Core change details
A concise summary and the intended behavior are enough to begin.
Evidence files (Optional)
Add changed files, diffs, contracts, schemas, configuration, requirements, or dependency notes when available.
Relevant text files only. Maximum 250KB per file and 600KB total.
Ready to trace the impact?
Start with the required fields. Additional context improves evidence confidence and result specificity.
What this review returns
Where a change lands, and what to verify
Affected areas
The surfaces a change is likely to touch, derived from what you describe rather than assumed.
Risks worth checking
Specific things that could break, each tied to the part of the change that causes it.
Verification steps
What to test before release, in the order that finds problems soonest.
Open questions
Detail the review needed and did not have, stated plainly instead of filled in.
This is advisory. It does not approve a release, and it cannot see your code — only what you describe here.