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 repositories are public, so you can inspect the pull requests produced by that process.

Plan
Build
Merge

Public record

2,400+pull requests opened by ProPR
2,100+of them merged
690+merged PRs building ProPR itself
14+ moof daily dogfooding

A public implementation, carried through review and merge.

Issue #1601 and implementation pull request #1613 anchor the example. Purpose-edited comments compress ProPR's follow-up, Ultrafix, and human-merge controls into one readable thread.

  1. 01
    The issue becomes a pull request.

    The opening record links the issue and captures delivered scope, verification, model, token use, cost, and subscription capacity.

  2. 02
    Feedback and review drive new commits.

    A human request produces a focused commit. A manually started Ultrafix loop scores the branch, applies its findings, and reviews it again.

  3. 03
    The maintainer controls the merge.

    The second review reaches 8/10, checks pass, and the final decision remains a standard GitHub action.

Open source PR #1613
A purpose-edited capture rendered from public GitHub pull request 1613, showing its execution record, a human follow-up, ProPR's response, a manually started Ultrafix loop, detailed 7 out of 10 review, corrective commit d5ef628, detailed 8 out of 10 review, and the human merge into main.

Open the pull requests and read them yourself.

Every one started as an issue, ran in an isolated workspace, opened a pull request, and went through review — the exact loop this product describes. These repositories are public.

integry/propr

690+ merged

ProPR builds and maintains its own codebase through ProPR. Regular PR #1613 implemented setup-wizard issue #1601 as one part of its larger plan.

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 expose scoped plans, agent commits, scored review findings, follow-up changes, and checks. GitHub preserves each action in the discussion. Point the same workflow at your repository in two commands.

Install in two commands →