KodaCode
Coming soon
Docs/Features

Code review

/review runs security, quality, best-practice and project-rules reviewers plus dependency and secret scanners. It then challenges every finding before you see it.

Run a review

CommandReviews
/reviewUncommitted changes
/review mainChanges against a branch
/review a1b2c3dOne commit
/review --allThe whole project
/review-securityOnly for security vulnerabilities
/review-qualityOnly for correctness and quality
/review-practicesOnly for best practice
/review-rulesOnly against the project's rules and AGENTS.md

The variants take the same targets as /review. A /review line can end a longer message. A folder that isn't a git repository has no change to review.

How it works

  1. Scanners run first: osv-scanner for dependency vulnerabilities and Betterleaks for secrets.
  2. Context reads the project once. It writes the brief that every review part shares: untrusted input, security patterns and conventions.
  3. The review parts read the change. The list below says what each part does.
  4. Challenge tries to prove each finding wrong. It drops findings that score under the threshold (8 of 10 by default).

The review parts:

  • Security finds vulnerabilities that the change introduces, one class at a time. It also sorts the scanners' hits.
  • Quality finds correctness and maintainability problems.
  • Practices finds departures from the language's and framework's best practices.
  • Custom checks the change against the rules in .koda/review-rules.md, AGENTS.md and CLAUDE.md, and only those.

The review lists findings worst first, as critical, high, medium or low. Their categories are Security, Correctness, Quality, BestPractice and CustomRule.

Review findings

The Review findings card lists each finding with its file and line. For each finding you can choose:

  • Apply suggestion. KodaCode keeps a suggested patch only if git apply --check accepts it.
  • Fix it for me.
  • Ask.
  • Dismiss, with a reason.
  • Mark fixed or Reopen.

Open in browser opens the full review, with its diff, as a page on disk. KodaCode saves reports in .koda/reviews/.

After every turn

When a turn changes files, a Scan of this turn's changes card shows what the secret and dependency scanners found. Review these changes runs the full review. To run a full review after each turn that changes files, enable Review every turn on a project's Runs on chip.

Settings

Code review settings set these values:

  • How many review agents run at once (1 to 4).
  • The challenge threshold.
  • Whether KodaCode challenges each finding separately.
  • What KodaCode checks suggested fixes against.
  • Where the scanners come from.

The Agents screen holds each review agent's model and instructions.