Skip to content

Review Agent ​

Review agent icon

Code review specialist that evaluates pull requests for correctness, security, intent alignment, style, and documentation currency.

How the agent works ​

The review agent is triggered when a PR is opened or updated. It follows the same pre-script / sandbox / post-script pipeline as the other agents.

  1. Pre-script validates inputs and fetches PR metadata.
  2. Sandbox — the agent runs the pr-review orchestrator skill. The orchestrator triages the change, then dispatches specialized sub-agents in parallel — each covering a distinct review dimension (correctness, security, intent & coherence, style & conventions, docs currency, and optionally cross-repo contracts). Sub-agents run concurrently and return structured findings. The orchestrator collects, deduplicates, and synthesizes findings across dimensions, runs PR-level checks (scope authorization, protected paths), and produces a structured JSON review result. The agent cannot push files, edit code, or push — it is strictly read-only.
  3. Validation loop — the output is checked against a schema, with up to 2 retry iterations if the output is malformed.
  4. Post-script posts the review on the PR. When REVIEW_RISK_ASSESSMENT_ENABLED is on (the default) and the result JSON omits risk_assessment, fullsend post-review posts a sticky diagnostic (Risk assessment unavailable this run) so a missed risk-assessment pre-pass is never silent. Workflow logs also carry fullsend:persona: invoke/complete/error/reject/skip markers for each named persona.

If a prior review exists (e.g., re-review after fixes), it is injected into the sandbox so the agent can assess whether previous findings were addressed.

How it helps ​

  • Every PR gets a thorough review within minutes, regardless of team availability.
  • Reviews cover security, correctness, intent & coherence, style, and docs currency — dimensions humans sometimes skip under time pressure.
  • The structured output format makes it easy to see what was flagged and why.

Commands ​

CommandWhereEffect
/fs-reviewPR commentTriggers a review on the PR (per-repo installs only; standalone issues are ignored)

Requires triage-level repository permission or higher (triage, write, maintain, or admin). Mutation stages such as /fs-fix still require write or higher.

The /fs-review command does not accept arguments. The review agent also runs automatically when a PR is opened, synchronized (new commits pushed), or moved out of draft by a user with triage-level repository permission or higher. On GitLab, automatic review fires when the cron poller sees an MR whose created_at is newer than the watermark (up to one poll interval of delay). Native merge_request_event dispatch was removed; all GitLab events route through the poller. Push-to-open-MR (GitHub synchronize) is not auto-detected; comment /fs-review to re-review after new commits.

Control labels ​

These labels are applied by the review post-script based on the review outcome.

LabelMeaning
ready-for-reviewWorkflow state marker on the PR. Applied by the code agent post-script after pushing. In per-repo installs, triggers review when applied to a PR.
ready-for-mergeThe review agent approved the PR. No blocking findings.
requires-manual-reviewThe review agent found issues that require human judgment — it could not confidently approve or reject.
rejectedThe review agent rejected the PR and the post-script closed it.

When the review agent requests changes (without rejecting), no outcome label is applied — the pull_request_review event triggers the fix agent directly.

Stale outcome labels from prior review runs are removed before the new one is applied.

The issue-labels skill may also apply contextual labels (e.g., area/api, priority/high) but these are informational -- they do not control agent behavior.

Configuration and extension ​

Skill: issue-labels ​

The review agent includes the issue-labels skill to discover your repo's labels and apply them to PRs during review. This is the same skill used by the triage agent -- overloading it affects both agents.

To overload the built-in skill, create your own issue-labels skill in .agents/skills/issue-labels/SKILL.md and symlink .claude/skills to .agents/skills so it's discoverable by both fullsend and local agent tooling. You can also overload it at the org level using config-driven agent registration -- see Bring Your Own Agent.

See Configuring with AGENTS.md and Configuring with Skills.

Variables ​

VariableDescriptionDefaultValid values
REVIEW_FINDING_SEVERITY_THRESHOLDMinimum severity for findings to include in the review. Findings below this level are omitted from both the narrative body and the posted inline comments.lowinfo, low, medium, high, critical
REVIEW_RISK_ASSESSMENT_ENABLEDGates the ADR 0089 risk-assessment pre-pass and the missing-assessment diagnostic. When on and the result JSON omits risk_assessment, fullsend post-review posts a sticky "Risk assessment unavailable this run" comment.truetrue/false (also accepts 0/no/off as false)

REVIEW_FINDING_SEVERITY_THRESHOLD is read inside the review agent's sandbox, so set it in the harness's env.sandbox (the upstream default lives in harness/review.yaml).

REVIEW_RISK_ASSESSMENT_ENABLED is different: fullsend post-review reads it directly from the runner process's own environment, not the sandbox. Set it in the harness's env.runner instead — setting it only in env.sandbox will not change the post-script's diagnostic behavior.

To override either variable per repo or org, use base: composition rather than the CI workflow env: block — workflow env: is reserved for infrastructure plumbing (see Architecture for details on harness composition and workflow-env conventions).

The review agent omits findings below the threshold from its output. The post-script also filters the structured findings array as defense-in-depth. When filtering removes all findings from a request-changes or reject verdict, the post-script downgrades the verdict to comment (applying the requires-manual-review label).

Source ​

fullsend-ai/agents — harness/review.yaml