GitHub App

Every pull request reviewed. Every fix a PR.

Codna reviews every pull request and approves a clean diff. Ask for a fix from an issue label, a comment or a red check, and Codna opens the pull request for you to merge.

Install appRead docs

How it works

From pull request to verdict. From issue to fix PR.

01

Install on repos

Install on your account or organization and pick the repositories. Link the install to your Codna account for managed fixes, or add your own key.

02

Review every pull request

Codna posts findings with severity, category and confidence, up to ten at 0.75 confidence or higher, with suggested changes inline. A clean diff gets an approval. Re-reviews cover only new commits.

03

Open fix PRs

Trigger a fix from the codna-fix label, an @codna fix reply on a finding, or a red check suite. Codna triages a red suite first, so an infrastructure failure costs nothing.

04

Keep control

Codna never merges. Branch rules, required checks and your review stay in charge. Admins can turn automatic fixes off for the organization.

Comment commands

Comment to run Codna.

Two verbs, at the start of a line. Fixes need write access to the repository, and a fork gets the suggested change instead.

@codna review
@codna fix        # reply on a Codna finding

labels: codna-fix · codna-secure
PR evidence

Every PR explains itself.

Every fix PR states the issue, the root cause, the symbols touched and a confidence score, and asks for review before merging. Commits come from codna-ai[bot].

Root causeone sentence
Confidence0 to 100%
Check runcodna review · codna fix · codna secure

Frequently asked

Inline findings with severity (high, medium, low), a category (correctness, security, performance) and a confidence score, with a suggested change where one applies. A clean diff at medium and high gets an approval that counts toward branch rules; otherwise Codna comments. It never requests changes. Turn approvals off with review.approve: false.

The codna review check appears as queued the moment you push. A superseded commit ends neutral and the new head is reviewed. When a required check is failing, the review says so next to the verdict: the verdict is about the diff, not a merge go-ahead. Merge queues inherit the pull request's verdict.

Add the codna-fix label. Codna maps the repository for zero tokens, fixes from an evidence bundle, and opens a pull request stating the issue, root cause, symbols and confidence. If the patch does not clear the risk gate, nothing is pushed and Codna says why.

A linked account includes a managed-model allowance of about $5 a month. Add your own key on the account page for uncapped, self-billed use. On 87 measured cases a verified fix averaged about $0.02 of model spend.

Reviews run within 4 to 20 minutes depending on pull request size; a timed-out review says so and asks for @codna review or a smaller PR. One CI-failure fix per pull request head per day. Jobs end after 30 minutes. Hosted test runs use pytest; other runners end neutral with a hint to set fix.test_command. @codna fix needs write access and does not run on fork pull requests.

Short-lived, repository-scoped tokens per job. Review: contents read, pull requests write, checks write, statuses read. Fix: contents, pull requests, checks, issues and workflows write. Secure: contents and security events read, checks and issues write. The review agent holds no write token.