AI contributor assistant

Go Rabbit turns focused Go issues into PR-ready changes

Choose an approved repository, pick an open issue, watch the agent scan, patch, validate, explain, and prepare a clean pull request summary.

Start a runView workflow
4Approved repos
12Run stages
120sValidation cap

go-rabbit.run

Run Setup
golangci/golangci-lint
#6420 gosec: G602 false positive
Run Contributor Agent
completed repository scan complete
running generating patch draft
skipped validation timed out after 120s
completed PR summary ready
PR Summary

Fix: gosec G602 false positive

  • Changed package files
  • Captured validation notes
  • Prepared draft PR body
01

Parse issue

02

Classify difficulty

03

Find relevant files

04

Read tests

Architecture

How a selected issue becomes a reviewed patch

The browser stays focused on review and approvals. Server-side tools own GitHub access, temporary repository workspaces, model calls, validation commands, and PR creation.

Mermaid architecture

Review surface

Everything needed before a maintainer sees the PR

Grounded context

Issue body, comments, repository tree, nearby files, and tests flow into patch generation.

Validation trace

Live command output, elapsed time, timeout skips, and retry logs remain visible in the terminal.

Clean export

PDF reports capture the PR summary, diff explanation, validation results, and CLI trace.

Report preview

Review a saved Go Rabbit PDF report

Generated on 1st local run

This sample report shows the output format for an agent run: summary, changed files, validation notes, diff explanation, and raw trace.

Open sample report

Setup

Run locally in four steps

Go Rabbit needs Node, GitHub CLI auth, a GitHub token for issue reads, and model credentials for patch generation.

01

Install

npm install
02

Configure

cp .env.example .env.local
03

Authenticate

gh auth login
04

Start

npm run dev

Deployment runtime

Hosted UI is separate from the contributor worker

The Vercel deployment can serve the interface, fetch GitHub issues, render reports, and show the workflow surface. Full contributor runs need a runtime with native CLIs available on PATH.

git

Clone, fetch, checkout branches, check patches, diff, commit, and push.

gh

Authenticate GitHub, create or attach forks, and open draft PRs.

go

Run Go validation commands such as package tests and project checks.

make

Run Makefile validation when a target repository requires it.

Vercel serverless functions are not a reliable runtime for full agent execution because these binaries may be unavailable and long-running validation can exceed serverless limits. Run the contributor worker locally or on a VM/container image that installs these tools.

Agent workspace

Run Go Rabbit

Start with an approved repository and an open issue. The right-side terminal shows each useful agent event while the run is active.

Run Setup

Agent Run Trace

  1. 1Parse issue
  2. 2Classify difficulty
  3. 3Find relevant files
  4. 4Read tests
  5. 5Generate fix plan
  6. 6Generate patch
  7. 7Apply patch
  8. 8Run validation
  9. 9Retry once if needed
  10. 10Explain diff
  11. 11Draft PR summary
  12. 12Manually create PR with message, diagram, and description

Agent Terminal

go-rabbitidle

infoSelect a repository, fetch open issues, then run the contributor agent.