agentmods.dev

sova: Command for Claude Code

.claude/commands/request-review.md

request-review is a command for Claude Code from xsovad06/sova. It costs 12 tokens per session (408 once invoked), scanned A, original, Apache-2.0.

A command that drafts a short Slack message asking a team to review a pull request. Slack is a team-chat application, and a pull request is a proposed code change awaiting review.

In plain words
What is it for?
Use it to identify a pull request from its number or current branch and produce a brief message for the review group.
Why use it?
It extracts the pull request’s title, link, and summary so you can request review without writing the message manually.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is xsovad06/sova's own configuration. It tells Claude Code how to work on sova itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sova configures →

not rated 2repo yesterday A scan 12 tokens original Apache-2.0
View source ↗ xsovad06/sova
Reuse

Borrowing it

Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.claude/commands/request-review.md
Clone the repo
git clone --depth 1 https://github.com/xsovad06/sova

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.

agentmods badge for request-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/xsovad06/sova/request-review/github.svg)](https://agentmods.dev/commands/xsovad06/sova/request-review)
Your own site
<a href="https://agentmods.dev/commands/xsovad06/sova/request-review"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/request-review/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 request-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsovad06/sova/request-review"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/request-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 408 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00408
Opus 5.5 $0.00005 $0.00163
Sonnet 5.5 $0.00002 $0.00082
Haiku 4.5 $0.00001 $0.00041

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

Security

Grade A, and why

request-review 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 2mo 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/request-review.md · 35 lines

What it actually says

Draft a Slack message for requesting a PR review. Can be used with a PR number argument or auto-detect from the current branch.

Instructions

  1. Identify the PR:

    • If a PR number is provided as argument, use it: gh pr view $ARGUMENTS --json title,url,body
    • Otherwise, detect from current branch: gh pr view --json title,url,body
    • If no PR found, inform the user

  2. Extract key info:

    • PR title and URL
    • One-line summary of what the PR does (from the title or body, in plain language)

  3. Draft the Slack message:

    • Format: casual, very short — tag @pr-review-group1, a few words from the PR title, PR link
    • Vary the greeting naturally (Hi, Hey, Hola, etc.)
    • No emojis, no bullet points, no formatting — keep it under 20 words (excluding the link)
    • Examples of good messages:
      • Hi @pr-review-group1, PR for review — add name filtering indexes: <link>
      • Hola @pr-review-group1, PR for review — audit logging for role bindings: <link>
      • Hey @pr-review-group1, PR for review — unify V2 name filtering: <link>

  4. Move JIRA tickets to Code Review:

    • Extract JIRA ticket numbers from the PR title/body (format: [RHCLOUD-XXXXX] or JIRA links)
    • Move each ticket: jira issue move RHCLOUD-XXXXX "Code Review"
    • Report which tickets were moved

  5. Output:

    • Print the draft message in a code block so the user can copy-paste it directly
    • Report which JIRA tickets were moved to Code Review
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. 2mo ago First seen · 35 lines · 12 tokens per session scan A 22ceab501f4a

Subscribe to this mod's changes

request-review is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 408 once invoked, about $0.0000 per session on Opus 5.5. 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-31.

Code reviewai-agentsautomationautonomous-developmentclideveloper-tools
Related

Other commands, from other repositories

greptile-review

Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.

opensesh/KARIMO · 0 tokens

review-branch

Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.

damusix/atomic-claude · 35 tokens

review

Review current changes for correctness, style, and potential issues.

Goldziher/ai-rulez · 11 tokens

advanced-code-review-context

Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.

axiomantic/spellbook · 19 tokens

code-review-give

Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.

axiomantic/spellbook · 17 tokens

mach12:issue-review

Read a GitHub issue and all comments, review the implementation plan, and present findings.

LeanAndMean/scramjet · 17 tokens