Release Engineer
Menu

RELEASE INTELLIGENCE

Understand the change.Own the release.

Claude-powered release-risk review for public GitHub pull requests. Identify API contract changes, security concerns and testing gaps, with evidence tied to the reviewed commit.

See a sample report
RELEASE / SIGNAL
ILLUSTRATIVE TOPOLOGY

ILLUSTRATIVE CHANGE

A response changes.

Release[]
{ items: Release[] }

REVIEW THE CONSEQUENCE

Follow affected paths.

Caller code beyond this patch has not been inspected.

Explore an illustrative finding

Trace relationships within a defined review boundary.

Conceptual visualization · No live telemetry

01 / FROM DIFF TO DECISION

The change. The evidence.
Your next decision.

Connect what changed to what needs checking. Evidence, uncertainty and next steps in one view.

Illustrative example — not a live analysis.

Release Engineer/Review workspace
INTERACTIVE EXAMPLE
TSsrc/api/releases.ts+1 −1

SOURCE / RESPONSE CONTRACT

Wrap the release response

An authored change to GET /releases

08export async function GET() {
09 const releases = await listReleases();
10
11− return Response.json(releases);
12}
13// Callers outside this patch are not shown.

Select the added line to trace its potential release risk.

THE CONTRACT BOUNDARY
Release[]{ items: Release[] }

Same data. A different shape for every caller.

Release-readiness reportPOTENTIAL RISK
High risk · Human review needed01

BREAKING CHANGE / API CONTRACT

The response shape changed.

GET /releases changes from an array to an object with an items field. A caller expecting an array could fail.

Callers outside the supplied patches have not been inspected. This is a concern to verify, not a confirmed regression.

Verify the API contract and affected callers. Add a compatibility test or document a coordinated migration before merging.

Evidence → Inference → Verification
THE SIGNAL IS A STARTING POINT.

A structured second perspective, with the limits kept in view.

YOUR PUBLIC PULL REQUEST

Bring your next change.

Get a structured second opinion, tied to the reviewed commit.

Analyze a pull request

Free · 10/month

10 of 10 free reviews left this month · This browser

View plans

Public PR contents are sent to Claude. PR contents and reports are not persisted by the application. Privacy

IN USE / WEBHOOK REVIEW

A finding.
A concrete improvement.

A developer reported tightening Base64 secret validation and adding two edge-case tests after reviewing the report.

Read Daniel’s review outcome ↗︎
“Caught a missing validate=True in my base64 secret decoding right after I wrote the code. The tool doesn’t run tests, and it says so — that honesty is why I trust the rest of the report.”
Daniel Reyes Backend Developer · Published with permission

02 / THE REVIEW PIPELINE

An extra perspective.
A human decision.

For the moments when a small diff can carry a much larger consequence.

AI adds a perspective.
You own the release decision.

  1. 01

    GITHUB / PUBLIC ONLY

    Connect a public PR

    Start with a GitHub URL. Retrieve public metadata and changed-file patches, pinned to the reviewed head SHA.

  2. 02

    CONTEXT / EXPLICIT LIMITS

    Bound the review context

    Select changes within deterministic byte limits. Omitted files and shortened patches remain visible in the report.

  3. 03

    ANTHROPIC / SERVER ONLY

    Reason with Claude

    Surface potential regressions, security concerns, breaking changes and missing tests. Validate the structured response.

  4. 04

    RELEASE / HUMAN JUDGMENT

    Verify before merging

    Inspect the evidence, check affected callers and run your tests. The release decision stays with you.

03 / ENGINEERING, IN THE OPEN

Built on boundaries
you can inspect.

Credibility comes from boundaries you can inspect, and results you can question.

Explore the evidence index ↗︎
01

Real Claude integration

The official Anthropic SDK runs on the server. API credentials stay there.

Review engine ↗︎
02

A defined context boundary

Deterministic selection and byte limits. A partial context cannot receive a merge recommendation.

Context policy ↗︎
03

Validated, constrained output

Strict schemas, prompt-injection defenses and explicit coverage limitations.

Output safeguards ↗︎
04

An inspectable implementation

Public source, browser tests and a dated evaluation record that includes its failures.

Source & checks ↗︎

04 / MEET THE FOUNDER

Engineering judgment,
built into the product.

Ozan Kenan Güngör

Founder & developer

Ozan builds and operates Release Engineer in Ankara, Türkiye. Launched in October 2026, the project helps developers review public pull requests with clear evidence, focused findings and practical next steps.

Meet the founder ↗︎Explore a documented PR review ↗︎Share beta feedback ↗︎founder@releaseengineer.tech

YOUR NEXT RELEASE / A SECOND PERSPECTIVE

Your next pull request.
A clearer second opinion.

Analyze a public PR

Public GitHub pull requests · No account required