PATCHFLOW / REPAIR ENGINEEST. 2026
$ patchflow init
0%
CLONING - ANALYZING
PATCHING - READY
REPAIR ENGINE / ONLINESCROLL TO REVIEW THE PATCH ->

SHIP FIXES,NOT BUGS

Paste a repo and issue. Patchflow reproduces the failure, writes the smallest safe patch, validates it, then opens a reviewable Pull Request.

( SCROLL )

Every red CI build should be handled by a repeatable repair pipeline: reproduce the failure, make the smallest safe change, prove it with tests, then ship a pull request.

THE REPAIR
PIPELINE

DRAG / SCROLL HORIZONTALLY
STAGE_01 / QUEUED

Queued

Capture the repository, branch, issue statement, expected result, and optional reference command before any runner work begins.

$ intake review --scope tight
01
STAGE_02 / ANALYZING

Analyzing

The System prepares the repository in a local sandbox and inspects the reported failure before editing code.

$ inspect issue -> failure located
02
STAGE_03 / PATCHING

Patching

Patchflow pushes the smallest defensible code change. The product bias is a readable diff, not broad refactoring.

diff --stat -> -1 / +1
03
STAGE_04 / REVIEWING

Reviewing

An automated review gate checks the proposed change without executing requester-supplied commands, then records user-visible logs and artifacts.

$ review patch -> approved
04
STAGE_05 / SHIPPED

Shipped

When the run succeeds, the GitHub App creates a branch and pull request so the user keeps final merge control.

PR opened -> ready for review
05

ONE BUG.
ONE LINE.
ZERO NOISE.

The value is not just writing code. The value is restricting the change to the exact failure, making the diff readable, and keeping merge authority with the repository owner.

packages/shared/utils/format.ts-1 / +1
38// parseLocale can return undefined after dependency update
39export function formatPrice(input: string) {
40 const locale = parseLocale(input).locale;
40 const { locale = DEFAULT_LOCALE } = parseLocale(input) ?? {};
41 return new Intl.NumberFormat(locale, opts);
42}
review gate passed / 0 regressionsPR ready for review
0%

PRs only after review

0

observable repair stages

0

credit per repair attempt

0

seat pricing or subscription lock-in

F.01

Inspect First

Runner work starts by narrowing the failure in an isolated checkout.

F.02

Minimal Patch

Changes stay inside the issue scope with no opportunistic rewrites.

F.03

Pull Request Delivery

Every successful fix lands as a GitHub branch and reviewable PR.

F.04

CLI Handoff

Task packets are processed by the System instead of browser-triggered shell execution.

F.05

Second-Level Logs

Clone, analysis, patch, review, and delivery events are visible to the user.

FIX

THE NEXT RED BUILD
CAN START HERE.

START A FIX

$ patchflow fix https://github.com/your-org/your-repo