Skip to main content

DOS Code Review / Built for GitHub

Better code. Before the merge.

Catch security gaps, broken logic, and API regressions. Get evidence and suggested fixes, right in your GitHub pull request.

Connect your GitHub repositories.

GitHub PR exampleIllustrative example
acme / storeOpen

Scope order access to its owner #42

src/api/orders.tsFiles changed

Original diff

async function getOrder(req) {
  return db.orders.find(req.params.id)
}
DOSDOS Code Reviewbot

IMPORTANT · Missing owner authorization

Any signed-in user can read another user's order.

Challenged by the Critic
Reviewer + CriticInline findingsYour repo rules

Find real bugs

Security, logic, and API contracts.

Check the evidence

Candidate findings go to the Critic for verification.

Fix in GitHub

Inline comments, suggested fixes, your repo rules.

Beyond a green check

A passing build can still ship a bug.

Explore three small changes with real consequences. Each example connects the code to the failure it can cause.

Illustrative example

api/orders.ts

- db.orders.find({ id: req.params.id })
+ db.orders.find({
+   id: req.params.id,
+   userId: req.user.id
+ })

An ID is not permission.

What breaks

Looking up an order by ID alone lets one signed-in user access another user's order.

What to change

Bind the lookup to the authenticated owner.

Fits your repository

Your conventions. Your final call.

Give the reviewer the context your team uses. Keep discussion, suggestions, and merge decisions in your existing workflow.

Findings and fix proposals appear in GitHub. You decide which suggestions to apply; Code Review does not automatically commit or merge them.
.dos/review.mdRepository guidance
  • Check ownership before returning account data.
  • Preserve public API response shapes.
  • Report a concrete failure scenario.

Review on demand

Ask for another review, discuss a finding, or request a fix proposal in the PR.

/review/fix/describe
@dos Explain why this lookup needs an owner check.

From pull request to a better merge.

Read the docs
  1. 01

    Connect

    Choose your repositories.

  2. 02

    Review

    Reviewer checks the diff. Critic verifies candidate findings.

  3. 03

    Decide

    Apply useful fixes. You own the merge.

Evidence before advice

  1. 01

    Reviewer

    Inspects the diff and identifies candidate defects.

  2. 02

    Critic

    Challenges candidate findings against the code and failure scenario.

  3. 03

    GitHub

    Keeps actionable findings and fix proposals beside the changed lines.

The Critic runs when the Reviewer has candidate findings. Your team decides what to apply and merge.

A few things to know.

Does it replace a human reviewer?

It adds another review layer. Your team still owns design decisions, test coverage, and the final merge.

Will it automatically change my code?

Findings and fix proposals appear in GitHub. You decide which suggestions to apply; Code Review does not automatically commit or merge them.

Can I tailor reviews to my repository?

Yes. Add .dos/review.md for repository-specific guidance, and manage connected repositories and review settings in the dashboard.

Is my code used to train models?

No. DOS does not train on your code. Code Review sends the changes, the files a review reads and, where enabled, the pull request title, description and a linked issue to a model, only to perform the review, summary or command, and providers that train on customer code are not used. DOS does not use your code or review results to evaluate or improve its services unless you opt in, and no opt-in is offered today. Comments are posted on GitHub; if you set up Slack or Telegram notifications, the start of the review report, which can include file paths and code excerpts, with the repository, pull request number and link, is sent there too. Read the full privacy statement

Pricing

Make the next merge a better one.