Bug Review

Find the bugs before your reviewers do. Bug Review checks your change for logic errors, missed edge cases, invalid inputs, concurrency problems, and broken code signatures, and returns numbered findings with file locations and severity.

Book a demo All use cases

One verdict. Numbered findings.

Find bugs such as logic errors, missed edge cases, invalid inputs, concurrency problems, and broken code signatures. Returns an approval verdict and numbered findings with file locations and severity.

/cloudaeye:inspect

What it checks

Logic errors
Edge-case handling
Input validation
Error handling
Concurrency safety
Code signatures and naming consistency
Code clarity and syntax style

What comes back

verdict: request_changes3 files changed

1A second partial refund can exceed the remaining balance.Highpayments/refund.py:42 · logic
2Two refunds on one order can both read the old balance.Mediumpayments/ledger.py:88 · concurrency
3Negative refund amounts are not rejected.Lowapi/refunds.py:19 · input validation

Which findings do you want fixed? Nothing is edited until you reply.

The routine check
after every task.

Run it when a coding task is finished, before you commit, or on an open pull request. You get a clear verdict and findings you can act on by number.

Catch the caller your change broke.

A changed function signature is checked against its callers across the repository, so a finding can point at a file you never opened.

Changed signatureChecked against every caller
FindingCan sit outside your change
ScopeThe whole repository

Explore Multi-repo Context

No calls to code that is not there.

Every name your change calls is checked against the repository. A call to a function the same change deleted, or to a name one typo away from a real one, is a finding.

Deleted functionStill called, flagged
TypoOne letter off a real name
CheckedEvery name the change calls

See an example

Part of done, after every task.

It is the routine pass, cheap enough to run after every coding task. Point it at one path, or keep only the serious findings.

AfterEvery coding task
Same change againStored result, no cost
FocusA path, or --high only

See the commands

Fix by number, or track it.

Every finding comes back numbered, with its file, line, and severity. Use the numbers to fix findings or file them as tickets. Nothing changes until you answer.

Each findingFile, line, and severity
Fix/cloudaeye:implement [1,3]
Track/cloudaeye:create-issue [2]

Explore Fix Suggestions