Intent checkIn testing
Does the PR do what its issue asked?
Forseti finds the linked work item, pulls out its acceptance criteria and rates each one met, unmet or unclear, with the file and line that shows it. It informs the review. It never blocks by default.
- metPartial refunds keep the remaining lines openrefund.ts:41
- unmetCustomer gets one email per refundnotify.ts:18
- unclearRefunds over £500 need a second approverno matching code
Advisory: intent never blocks a merge unless your policy says so.
How it works
Step by step.
Does the PR do what its issue asked? Evidence per criterion.
- 01LinkClosing references, issue links in the body, the branch name (feat/123-…), and Jira or Linear keys when connected.
- 02ExtractAcceptance criteria are pulled from the work item.
- 03RateA reasoning pass rates each criterion met, unmet or unclear.
- 04CiteEvery rating points at the code that supports it.
In detail
What it does, exactly.
- Evidence for every criterion, and an honest “unclear” instead of a guess.
- Advisory by default: it never blocks a merge unless you decide it should.
- On GitHub
- Intent section in the summary
- In the dashboard
- PR detail: criteria with evidence
Evidence per criterion
Not a vibe score: each criterion has its own status and its own file:line evidence.
“Unclear” is an answer
When the code doesn't settle it, Forseti says so instead of guessing.
GitHub Issues
Linked GitHub issues are read with the access Forseti already has. No extra setup.
Jira and Linear: ready
Built and tested against recorded responses. Connect your account to use them.
Works with
Next: Supply chainPut Forseti on your next pull request.
Connect GitHub in four clicks. Your first review starts by itself on your latest small open PR, priced before it runs.