agentmods.dev

assign-reviewers

assign-reviewers is a command for Claude Code from ParkerM2/create-claude-workflow. It costs 14 tokens per session (3,831 once invoked), scanned A, original, MIT.

A workflow for choosing code reviewers for a GitHub pull request. It matches changed files with team expertise and considers each person's review workload and availability.

In plain words
What is it for?
Use it to analyze an open pull request, select up to three reviewers, assign them, and optionally notify them through Slack.
Why use it?
It reduces manual reviewer selection and helps avoid assigning too much work to one person.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the claude-workflow plugin — 10 skills, 25 commands, 3 agents, 6 hooks shipped together

not rated 4repo 5mo ago A scan 14 tokens original MIT

Good fit Use it to analyze an open pull request, select up to three reviewers, assign them, and optionally notify them through Slack.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/parkerm2/create-claude-workflow/assign-reviewers
View source ↗ ParkerM2/create-claude-workflow
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/ParkerM2/create-claude-workflow

Made for: Claude Code.

Or install claude-workflow, the plugin that ships this one along with the rest of its 10 skills, 25 commands, 3 agents, 6 hooks.

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 assign-reviewers

README.md
[![agentmods](https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/assign-reviewers.svg)](https://agentmods.dev/commands/parkerm2/create-claude-workflow/assign-reviewers)
Your own site
<a href="https://agentmods.dev/commands/parkerm2/create-claude-workflow/assign-reviewers"><img src="https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/assign-reviewers.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,831 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.00014 $0.03831
Opus 5 $0.00007 $0.01916
Sonnet 5 $0.00003 $0.00766
Haiku 4.5 $0.00001 $0.00383

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

Security

Grade A, and why

assign-reviewers 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 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.

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/assign-reviewers.md · 485 lines

How it starts

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

Assign Reviewers Workflow

Intelligently assign PR reviewers based on code expertise (git blame), review load balancing, and team availability. Supports auto-assignment with Slack notifications.

Integration Points

  • GitHub MCP: PR analysis, changed files, review assignment
  • Memory: Team configuration, review load cache, expertise maps
  • Slack MCP: Notifications and requests to reviewers
  • Git: Historical blame data for expertise scoring

Workflow Phases

Phase 1: PR Analysis (Detection)

Identify the PR and extract changed files:

  1. PR Context Resolution

    • Accept: PR number, PR URL, or auto-detect from current branch
    • Format accepted:
      • PR number: 42
      • GitHub URL: https://github.com/org/repo/pull/42
      • Branch: auto-detect if current branch has open PR
    • Call GitHub API: GET /repos/{owner}/{repo}/pulls/{pr_number}
    • Extract: PR state (must be open), branch, title, creator

  2. Validate PR State

    • If draft PR: Ask confirmation to assign reviews (offer --draft flag)
    • If closed/merged: Exit with "Cannot assign to closed PR"
    • If already has max reviewers (3+): Ask if should replace or add

  3. Extract Changed Files

    • Call GitHub API: GET /repos/{owner}/{repo}/pulls/{pr_number}/files
    • Build file list with:
      • Path: src/auth/login.ts
      • Type: added/modified/deleted
      • Lines changed: additions + deletions
    • Filter: Ignore node_modules, vendor, lock files, generated code
    • Categorize by module: auth/, api/, ui/, shared/, etc.

  4. Flag Special Cases

    • All deletions: May need fewer reviewers
    • Single file/small change: Suggest 1 reviewer
    • Large refactor (50+ files): Suggest expert-level reviewers only
    • Documentation only: Suggest docs owner
    • Test changes only: Suggest QA lead

Verification Checklist:

  • PR exists and is open
  • Changed files list populated
  • File categories identified
  • PR creator identified (exclude from reviewers)

Read the full file on GitHub · 485 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 · 485 lines · 14 tokens per session scan A 738243ee23b8

Subscribe to this mod's changes

assign-reviewers is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 3,831 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.

Code review
Related

Other commands, from other repositories

sdd-init

Initialize SDD context — detects project stack and bootstraps persistence backend.

Gentleman-Programming/gentle-ai · 14 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

init

Install the formatters this repository needs, with every command visible before it runs.

azrtydxb/procoder · 16 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

argos

A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.

Dannykkh/skill-olympus · 21 tokens