What is review-deploy?

A command that deploys a pull-request branch to a temporary shared website for reviewing documentation changes. A pull request is a proposed code or content change before it is merged into the main project.

Use it for quick legal, compliance, product, or ad hoc review of normal documentation changes; larger site or interface work uses a separate staging command.

It gives reviewers a live preview of an article before the change is merged. The shared environment supports one review deployment at a time, so a new deployment replaces the previous one.

How SumoLogic/sumologic-documentation configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to SumoLogic/sumologic-documentation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SumoLogic/sumologic-documentation/main/.claude/commands/review-deploy.md

Clone the repo

git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/review-deploy/github.svg)](https://agentmods.dev/commands/sumologic/sumologic-documentation/review-deploy)

Your own site

<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/review-deploy"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/review-deploy/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/review-deploy"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/review-deploy.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 1,418 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01418
Opus 5.5	$0.00000	$0.00567
Sonnet 5.5	$0.00000	$0.00284
Haiku 4.5	$0.00000	$0.00142

Measured 1mo ago against content hash 96f1e868b833, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-deploy scanned grade A with 0 findings 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 1mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/review-deploy.md · 114 lines

How it starts

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

Review Deploy — Deploy PR to the Review Environment

Deploy a PR branch to the shared Pantheon review environment for quick, temporary article review (legal, compliance, product, ad hoc feedback).

When to use this command

You need a reviewer to preview a doc change in a live environment before merge, and the change is a normal content/article update rather than a UX/UI or site-wide feature.
A PR author or reviewer asks for a quick review link.

For staging larger UX/UI or site-wide feature work, use /stage-deploy instead — that targets the separate helpdocs environment reserved for feature previews.

Usage

/review-deploy {pr-number-or-branch}

Examples:

/review-deploy 6701
/review-deploy docs-update-jira-skill-fields

Review environment

URL: https://docs-review-sumo-logic.pantheonsite.io/help/
HTTP basic auth protected: Contact the docs team for credentials.
Single shared slot: Only one PR can be in review at a time. Deploying overwrites the previous deployment.
Build time: 20–30 minutes after the push triggers the workflow.

Workflow

Step 1: Resolve input to PR number

If input is numeric: validate the PR exists and is open with gh pr view {number} --json state --jq '.state'.
If input is a branch name: look up the PR number with gh pr list --head {branch} --json number --jq '.[0].number'.

You need the PR number for the review branch name, the PR comment, and to fetch the PR's head commit in Step 4. The branch name itself isn't needed for the push — see Step 4 for why.

Step 2: Check for conflicts

git ls-remote --heads origin 'refs/heads/review/pr-*'

Exclude review/pr-{number} for the PR you're currently deploying from the results — redeploying the same PR after new commits isn't a conflict with itself, and shouldn't trigger the overwrite comment below on the PR's own thread.

If one or more other review branches remain, identify who owns each one (gh pr view {n} for every match) and list all of them for the user:

Read the full file on GitHub · 114 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.

1mo ago Changed 96f1e868b833
2mo ago First seen · 114 lines · 0 tokens per session scan A 241045c8eba4

Subscribe to this mod's changes

review-deploy is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,418 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow Legal and compliance React documentation open-source

review-deploy next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
review-deploySumoLogic/sumologic-documentation	Command	42	yesterday	MIT	A	0	Claude Code
pr-readycostajohnt/oss-autopilot	Command	26	4d ago	MIT	A	45	Claude Code
prepare-releasesaeedkolivand/ai-job-hunter-app	Command	63	yesterday	Apache-2.0	A	20	Claude Code
review-diffChatbotXIO/ChatbotX	Command	1.1k	yesterday	none	A	26	Claude Code
review-fixesChatbotXIO/ChatbotX	Command	1.1k	yesterday	none	A	19	Claude Code
speckit.spex.submitrhuss/cc-spex	Command	122	3d ago	Apache-2.0	A	15	Claude Code
gitazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	20	Claude Code

sumologic-documentation: Command for Claude Code