Review a change for bugs and risk, with file, line, trigger, and confidence for each finding.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this for one pull request or diff at a time.
Read the description and linked issue first, then the diff, then the code the change calls and the code that calls it. Check the tests that cover it and whether CI has run. Note what could not be read, such as a truncated diff or a missing file.
Rank each finding as blocker, should fix, question, or style. For each give:
Keep style notes apart and short. Do not pad the list; say so when the change looks sound.
List what the review could not settle: behaviour that depends on data or config you cannot see, paths with no test, and assumptions the author should confirm.
Never say code is safe or a test passed without seeing the evidence, and do not invent a failure you cannot trace to a line. Do not approve, merge, or push to the branch; the reviewer of record decides.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.