AI pull request code review workflow blueprint

Inputs for the PR Diff Review workflow

Provide the following information when starting this workflow. Required inputs are validated before the first workflow stage runs.

• Diff

  Required

  Unified diff to review

  Type: String

• Repo

  Optional

  Optional repository name (for example, acme/backend)

  Type: String

• Pr Number

  Optional

  Optional pull request number

  Type: Number

• Pr Title

  Optional

  Optional pull request title or change summary

  Type: String

Input template

This request shape is generated from the blueprint's input schema. Angle-bracket values are placeholders; defaults and examples appear only when the source blueprint defines them.

{
  "diff": "<required string>",
  "repo": "<optional string>",
  "pr_number": "<optional number>",
  "pr_title": "<optional string>"
}

How the PR Diff Review AI workflow works

This engineering blueprint uses a sequential workflow with 2 agents, 0 functions, and 0 MCP servers. Open it in GraphN to customize the resources, inputs, and workflow behavior for your use case.

1. 1

   Analyze

   Agent using Code Analyzer

2. 2

   Synthesize

   Agent using Review Synthesizer

Blueprint resources and prerequisites

These are the actual agents, functions, and MCP servers declared by the blueprint. If an MCP server connects to an external system, configure the required connection and credentials in your GraphN workspace before running the workflow.

Workflow output contract

The completed workflow makes the following output available to downstream steps, applications, or API clients: