GreenPR

Problem

Dependabot and Renovate keep dependency maintenance moving, but a routine version bump can turn CI red because of ESM/CommonJS incompatibility, peer dependency drift, or Node engine changes. Engineers then reread logs, guess at a version pin, and still have to prove the patch is safe. Generic coding agents can suggest a fix, but a suggestion is not a green build or a reviewable pull request.

Solution

GreenPR is a repair studio that turns a failing dependency PR into a verified repair artifact. It diagnoses the failure from CI output, package.json, and source files; plans the smallest compatible change; applies it to a disposable workspace; runs real npm install and npm test; and emits a blast-radius report and GitHub-style PR draft.

Product features

  • Multi-fixture gallery for ESM/CommonJS, peer dependency, and Node engine failures.
  • Paste-workspace path for package.json, source, tests, and CI logs.
  • Streamed repair timeline: copy, diagnose, plan, patch, install, test, blast, and PR.
  • Before and after views with real command output.
  • Dependency delta, changed-file list, skipped-risk list, and baseline/result workspace fingerprints.
  • Downloadable proof capsule and durable repair history.
  • Deterministic mode for repeatable judging, plus a visible LIVE GPT-5.6 mode.

GPT-5.6 and Codex

GPT-5.6 live mode uses bounded tools to read files, inspect package metadata, write the proposed patch, run verification, and finish with a structured result. The model can propose a repair, but local code applies the patch and refuses to report GREEN unless real verification exits successfully. Model failure falls back to the deterministic planner and is labeled in the UI.

Codex built the diagnosis engine, repair planner, disposable-workspace verifier, fixture corpus, CLI, Studio server, SSE timeline, blast-radius schema, proof pack, and adversarial test gate. Human judgment kept the product focused on dependency PR repair with executable proof rather than another chat-based coding assistant.

Judge proof

Run npm ci, npm test, and npm run demo. Then run npm start, choose broken-dependabot, and click Run repair. The judge sees the original ERR_REQUIRE_ESM failure, the minimal chalk version repair, real install and test output, GREEN status, blast radius, and the generated PR artifact.

Built with

Node.js 20, TypeScript, npm, OpenAI GPT-5.6, Codex, node:http, and GitHub-style PR artifacts.

Built With

Share this project:

Updates