Pull Request Review with Claude Code: Result JSON Schema
A production playbook for pull request review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Developer tools teams
The problem
Developer tools teams need pull request review to run repeatedly against diffs, CI logs, ownership maps, and review policy. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Define the outer result contract once, let the pull request review skill own body.data, and reject terminal output that does not match the expected schema.
Tradeoffs and failure modes
Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For pull request review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Result shape
{
"schema_version": "argo.result.v1",
"summary": "pull request review completed",
"body": { "type": "pull_request_review", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo