Skip to content
autofeat

Code review for GitHub pull requests

Autofeat

A careful second reviewer for your pull requests.

Turn on a repository and open a pull request. Autofeat posts a plain-language review, and you choose what ships.

What it does

Autofeat reads your GitHub pull requests and posts a clear, plain-language review: what could break, what matters most, and how to fix it.

Careful by default.

How it works

Turn it on once. Then open pull requests as usual.

  1. Turn on a repository

    Install the GitHub App, then turn on the repositories you choose in the portal. Autofeat leaves every other repository alone.

  2. Open a pull request

    When a pull request is ready for review, Autofeat reviews it on its own. Drafts wait until you mark them ready.

  3. Choose what ships

    Findings arrive on the pull request as a comment and a check, in plain words, with suggested fixes. Then you decide.

Want a review on demand? Add the label autofeat:go to a pull request.

Want Autofeat to write the fixes too? That is opt-in and off by default: your repository policy and the service must both turn it on.

Read the quickstart

The portal

Every setting in plain view.

Autofeat settings for the sample acme organization, with review controls and Knowledge Base settings
Product preview with sample data

Example

Watch a sample review, step by step.

Example of an automatic autofeat review: a pull request is opened in a turned-on repository, autofeat reads the change and leaves two findings, then the merge decision stays with you.

Safeguards

You stay in charge.

Autofeat is careful by default. Every limit below is a setting you can see and change, and the safe choice comes first.

  • You hold the merge

    By default Autofeat stops before merging and marks the pull request ready. A person merges.

    merge_mode: stop_before_merge

  • Practice mode when you want it

    With dry run on, Autofeat reports status on the pull request but pushes no code, merges nothing, and adds no labels. It is the policy default; turning a repository on in the portal starts live reviews.

    dry_run: true

  • Hard spending limits

    Each pull request has caps on money, time, turns, and tokens. Work stops at the cap, and a warning comes before the money cap.

    budget

  • A stop label that wins

    Add autofeat:stop and Autofeat refuses every other action and cancels work in progress.

    autofeat:stop

  • Only where you invite it

    Autofeat sees only the repositories you install it on. On the hosted service, it reviews only the ones you turn on in the portal.

    GitHub App install

Hard spending limits

Work stops at the cap.

Spend cap
$25
Early warning
$10
Time cap
240 min
Turn cap
12
Token cap
2,000,000
Example limits from a real policy file. You choose your own.

Under the hood

For the technical folks on your team.

.autofeat/config.yml

version: 1identity: appentry_action: reviewautonomy:  merge_target: main  merge_mode: stop_before_merge  auto_approve: false  dry_run: true  require_green_checks: truepolicy:  mode: review_onlyagents:  default: claude  allowed: [claude, codex, kimi, grok-build]  billing: {claude: subscription, codex: subscription, kimi: subscription, grok-build: subscription}  models: {claude: {model: sonnet}}budget:  turns: 12  usd: 25.0  alert_usd: 10.0  minutes: 240security:  require_signature: true  trusted_actors: [OWNER]
An example policy from the schema. Keys you leave out use safe defaults, including a token cap of 2,000,000.
Sandboxed runs
Agents run in a sandbox as a separate user, and network access goes through an enforced allowlist.
Settings with clear limits
Account and repository settings in the portal provide defaults. The default branch's .autofeat/config.yml takes priority. Unknown keys are errors.
Signed steps
Run state and each next-step comment are signed, so nobody else can forge the next turn.
A record per pull request
Each pull request keeps a durable journal of what ran and why.
Your choice of agent
Use your own subscription or API key. Subscription agents cost nothing extra per run.
  • claude
  • codex
  • kimi
  • grok-build
  • opencode

Get started

Get a second pair of eyes.

Install the GitHub App, turn on the repositories you choose, and open a pull request to read your first review.

Review service is running