While you work
Uncommitted changes
Review the working tree before deciding what belongs in the next commit.
git diff --unified=3 Personal Review Available foundation
Review wherever you work, before you share.
Use the available Branch Diff foundation through REST or hosted MCP for uncommitted, staged, and branch-against-base changes. Portable entitlements and the complete iterative case workflow remain in development.
feature/auth-hardening
~$git fetch origin main
~$git diff --unified=3 origin/main...HEAD
Enjoyable review Complete
P1 src/auth.ts:42
Assignment bypasses the role check
The assignment evaluates truthy and grants admin access to every authenticated user.
P2 src/cache.ts:118
Failed writes remain marked as cached
2 actionable findings · style noise suppressed
Review moments
Meet the change before the pull request.
Review the smallest useful scope while the context is fresh, then act on focused findings before another reviewer is waiting.
Before commit
Staged changes
Check exactly what is staged while the change is still quick to correct.
git diff --cached --unified=3Before the PR
Branch against base
Compare the current branch with the base your team actually plans to merge into.
git diff --unified=3 origin/main...HEADAPI and MCP
One capability, wherever work happens.
REST and hosted MCP are two interfaces to the same review service, with the same finding policy and structured result.
For product integrations
REST API
Submit a unified diff, its primary language, and optional surrounding context. Receive a structured JSON result in the same request.
POST /v1/organizations/{id}/reviews/diff/sync For agents and IDEs
Hosted MCP
Connect an OAuth-capable MCP client and call review_diff. The client prepares the diff; Enjoyable evaluates it with the shared engine.
https://api.enjoyable.work/mcp For your workflow
Your adapter
Build the diff in a CLI, IDE, CI job, or internal tool, then render the returned findings wherever your engineers work.
diff in → structured findings outHosted MCP uses OAuth and does not inspect local files, fetch repositories, or compute diffs. Your MCP client or agent supplies the unified diff it wants reviewed.
Structured output
Enough detail to act. Easy to render anywhere.
Each response is designed for both people and the tools around them. A valid no-findings response is still an explicit completed result.
An exact location
Every finding includes the file path, line number, and side of the diff so clients can place it correctly.
Priority and category
P0–P2 severity and a concrete category make security, logic, reliability, race, and performance risks easy to triage.
Summary and suggested fix
A concise explanation describes the reachable impact, followed by a practical direction for correcting it.
Review the change before it becomes someone else's queue.
Join early access for Personal Review and help shape the portable fix-and-re-review workflow.