ProPR builds and maintains its own codebase through ProPR. Regular PR #1613 implemented setup-wizard issue #1601 as one part of its larger plan.
We build ProPR with ProPR.
Since May 2025, every product we ship has moved through ProPR's plan, isolated run, and PR review loop. Several of those repositories are public. Read the pull requests yourself.
Public record
A public implementation, carried through review and merge.
Issue #2901 and pull request #2934 are one task from a ProPR plan run in epic mode. The captures are unedited crops of the thread.
- 01The issue becomes a pull request.
Claude Opus 5.5 implements it. The opening record links the issue and lists the commit, model, tokens, cost, and subscription usage.
- 02Review drives the next commit.
Ultrafix starts from the task's settings. GPT-6 Astra scores the branch 6/10 and files merge blocker F1. The fix pass resolves it in one commit with a regression test.
- 03The goal decides the merge.
The re-review finds no blockers and scores 9/10, above the 8/10 goal. The issue carries the
auto-mergelabel, so ProPR merges it into the plan's epic branch. No one had to touch the thread.
Issue #2901 becomes a pull request

Ultrafix starts with the task's settings

Review: merge blocker F1, score 6/10

Fix: commit b4e98fb addresses F1

Re-review: no blockers, score 9/10

ProPR merges into the epic branch

Open the pull requests and read them yourself.
Each started as an issue, ran in an isolated workspace, opened a pull request, and went through review.
A production web game with leaderboards, OAuth, a live terminal UI, and Cloudflare Turnstile. PR #855 added supporter-only /promote titles across the header and leaderboard.
The companion subscription-capacity tracker. PR #77 implemented activity-based usage polling through local log monitoring.
An MCP server testing tool built with an early version of ProPR. PR #159 added OAuth 2.1 authentication for remote servers.
Inspect the workflow in the repository that ships it.
ProPR's own pull requests show scoped plans, agent commits, scored review findings, follow-up changes, and checks, with every action in the GitHub discussion. Point the same workflow at your repository in two commands.
Install in two commands →