Verification · Code review · Logic and correctness review
Logic bug review
Look for conditions, loops and state transitions that do not match intent.
How to build it
- Give the reviewer the change, its linked intent and the surrounding code.
- Ask for a finding only with a concrete input or state that triggers the bug.
- Post a finding only after a second check confirms the triggering input.
Signals in a repository
- A review workflow that runs pr-agent or claude-code-action on pull requests.
- Prompt or instruction files for the review bot in the repository.
- Review comments that name a specific input and the line it breaks.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.