review-respond

review-respond is a command for Claude Code from VorobiovD/air. It costs 0 tokens per session (6,330 once invoked), scanned C, original, MIT.

A command for responding to an existing code review by matching findings with local changes, checking whether fixes work, and preparing a structured response.

In plain words
What is it for?
Use it after receiving a pull-request review to verify fixes, inspect the updated diff, find additional changes, and prepare the review response.
Why use it?
It reduces the manual work of deciding which review comments were fixed, which remain, and whether new changes introduced more issues.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code; mentions Codex.

Part of the air plugin — 5 commands, 7 agents, 1 hook shipped together

Good fit Use it after receiving a pull-request review to verify fixes, inspect the updated diff, find additional changes, and prepare the review response.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/vorobiovd/air/review-respond
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/VorobiovD/air

Made for: Claude Code.

Or install air, the plugin that ships this one along with the rest of its 5 commands, 7 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-respond

README.md
[![agentmods](https://agentmods.dev/badge/commands/vorobiovd/air/review-respond/github.svg)](https://agentmods.dev/commands/vorobiovd/air/review-respond)
Your own site
<a href="https://agentmods.dev/commands/vorobiovd/air/review-respond"><img src="https://agentmods.dev/badge/commands/vorobiovd/air/review-respond/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-respond

Your own site · 80×15
<a href="https://agentmods.dev/commands/vorobiovd/air/review-respond"><img src="https://agentmods.dev/badge/commands/vorobiovd/air/review-respond.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,330 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.06330
Opus 5 $0.00000 $0.03165
Sonnet 5 $0.00000 $0.01266
Haiku 4.5 $0.00000 $0.00633

Measured 8d ago against content hash 91483731bf3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade C, and why

review-respond scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

find /tmp -maxdepth 1 -name 'air-*' -mtime +1 -exec rm -rf {} + 2>/dev/null
plugins/air/commands/review-respond.md · 423 lines

How it starts

The opening of the file, as written. The whole thing — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Respond Flow (--respond mode)

When --respond is passed, this flow automates the developer's side of the review cycle. It reads the existing review, classifies each finding based on local code changes, verifies fixes are correct, runs a self-check on the fix diff, detects additional changes, and posts a structured response that the reviewer's next re-review (Step 6) can parse directly.

Respond Step 0: Initialize Session Temp Directory

Before any /tmp write, mint a per-invocation session dir so parallel /air:review --respond runs (or a respond + concurrent review in two Claude Code sessions) don't overwrite each other's wiki files, diffs, or output comments. Capture the printed path and substitute it into every $AIR_TMP reference downstream.

If the orchestrator already minted $AIR_TMP (e.g. /air:review --respond routed through review.md Step 0), reuse it — don't double-mint. Otherwise mint a fresh dir:

if [ -z "$AIR_TMP" ]; then
  find /tmp -maxdepth 1 -name 'air-*' -mtime +1 -exec rm -rf {} + 2>/dev/null
  AIR_TMP=$(mktemp -d "/tmp/air-respond-XXXXXX")
fi
echo "$AIR_TMP"

Respond Step 1: Find the review and PR

  1. Detect the current branch's PR:
PR_NUMBER=$(gh pr view --json number --jq '.number' 2>/dev/null)

If no PR exists: "No open PR found on this branch. Push and create a PR first." and STOP.

  1. Fetch the review comment (same query as Step 2 in the main review flow).

IMPORTANT: API responses containing comment bodies have markdown with newlines and special characters. Do NOT store the full response in a shell variable — it corrupts control characters. Pipe directly to a parser:

gh api repos/<owner>/<repo>/issues/$PR_NUMBER/comments 2>/dev/null | python3 -c "
import json, sys
comments = json.loads(sys.stdin.buffer.read())
reviews = [c for c in comments if c['body'].startswith('## Code Review')]
if reviews:
    r = reviews[-1]
    print(f'ID={r[\"id\"]}')
    print(f'CREATED={r[\"created_at\"]}')
    lines = r['body'].split('\n')
    sha = next((l.split('Reviewed at: ')[1].strip() for l in lines if 'Reviewed at:' in l), 'NOT_FOUND')
    print(f'SHA={sha}')
"

Extract:

  • REVIEW_COMMENT_ID from ID= line
  • REVIEW_COMMENT_CREATED from CREATED= line
  • REVIEWED_AT_SHA from SHA= line
  • REVIEW_COMMENT_BODY — read from the API response inside the parser, not as a shell variable

Read the full file on GitHub · 423 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 423 lines · 0 tokens per session scan C 91483731bf3c

Subscribe to this mod's changes

review-respond is a command published in the GitHub repository VorobiovD/air (5 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,330 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.