Review your changes before you share them.

Enjoyable examines a unified Git diff and optional context, then returns focused P0–P2 findings anchored to changed lines.

Choose your path

Start with the interface that fits your workflow.

Both interfaces use the same focused diff-review contract. Hosted MCP is the quickest self-service path; REST access is currently provisioned.

Available

Add the remote server, complete OAuth in your browser, and ask your client to create and review a unified diff.

url

https://api.enjoyable.work/mcp

The review boundary stays explicit from the first command to the final engineering decision.

1 Produce the diff Use Git or another trusted client to select the working-tree, staged, branch, or pull-request change you intend to review.
2 Submit the evidence Send the unified diff, its primary language, and only the surrounding source context the review needs.
3 Inspect focused findings Review concrete security, correctness, reliability, race-condition, and severe performance risks returned as P0–P2 findings.
4 Revise and review again Apply the changes you accept, create a new diff, and run another review. You remain responsible for the decision to ship.

The current service supports developer-initiated Personal Review through two interfaces.

Hosted MCP over Streamable HTTP with OAuth and the review_diff tool.
Synchronous REST review for provisioned, entitled organization members.
Structured findings for 16 language identifiers with optional context and review controls.

Caller-supplied evidence only

Enjoyable does not reach into your machine or repository. Your client decides what to include and constructs the diff before review.

Connected pull-request execution and persisted review runs are still in development.
The service does not fetch repositories, compare branches, or inspect untracked files.
A review supports human judgment; it cannot guarantee that a change is safe or complete.