agentmods.dev

request-review

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

2 2d ago A scan 12 tokens original Apache-2.0
View the source file xsovad06/sova
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.

agentmods
npx agentmods add commands/xsovad06/sova/request-review
Clone the repo
git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

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. Scan, not verified.
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 $0.00012 $0.00408
Opus 5 $0.00006 $0.00204
Sonnet 5 $0.00002 $0.00082
Haiku 4.5 $0.00001 $0.00041

Measured 2d ago against content hash 22ceab501f4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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. 2d 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 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 408 once invoked, about $0.0001 per session on Opus 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.

Backend and APIsCode reviewGit and workflowai-agentsautomationautonomous-developmentclideveloper-tools
Related

Other commands, from other repositories

doctor

Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.

opensesh/KARIMO · 0 tokens

dashboard

Phase 3 monitoring — System health, execution insights, and velocity analytics.

opensesh/KARIMO · 0 tokens

run

Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.

opensesh/KARIMO · 0 tokens

merge

Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.

opensesh/KARIMO · 0 tokens

greptile-review

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

opensesh/KARIMO · 0 tokens

update

Check for and apply KARIMO updates from GitHub releases.

opensesh/KARIMO · 0 tokens