agentmods.dev

check-pr

check-pr is a command for Claude Code from Sagargupta16/claude-skills. It costs 14 tokens per session (407 once invoked), scanned A, original, MIT.

A pull-request check that reads GitHub’s current status, reviews, comments, and automated checks. A pull request is a proposed code change waiting to be reviewed and merged.

In plain words
What is it for?
Use it to review a pull request’s state, CI results, approvals, comments, conflicts, and merge blockers. When checks fail, it examines the start of the failing log and suggests a focused fix.
Why use it?
It gathers the information needed to decide whether a change can be merged, so you do not have to inspect each GitHub page separately. It also helps identify failing checks and unresolved review feedback.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the dev-workflow plugin — 1 skill, 7 commands, 2 agents shipped together

not rated 5repo changed 3d ago A scan 14 tokens original MIT

Good fit Use it to review a pull request’s state, CI results, approvals, comments, conflicts, and merge blockers. When checks fail, it examines the start of the failing log and suggests a focused fix.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sagargupta16/claude-skills/check-pr
View source ↗ Sagargupta16/claude-skills sagargupta.online
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/Sagargupta16/claude-skills

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 1 skill, 7 commands, 2 agents.

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 check-pr

README.md
[![agentmods](https://agentmods.dev/badge/commands/sagargupta16/claude-skills/check-pr/github.svg)](https://agentmods.dev/commands/sagargupta16/claude-skills/check-pr)
Your own site
<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/check-pr"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/check-pr/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 check-pr

Your own site · 80×15
<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/check-pr"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/check-pr.svg" alt="Reviewed on agentmods" width="80" 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 407 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.00407
Opus 5 $0.00007 $0.00204
Sonnet 5 $0.00003 $0.00081
Haiku 4.5 $0.00001 $0.00041

Measured 3d ago against content hash d88e9e2523b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

check-pr 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 3d 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.

plugins/dev-workflow/commands/check-pr.md · 35 lines

What it actually says

Live state

  • PR details: !gh pr view $ARGUMENTS --json state,mergeable,mergeStateStatus,isDraft,reviewDecision,statusCheckRollup,title,url 2>/dev/null || gh pr view --json state,mergeable,mergeStateStatus,isDraft,reviewDecision,statusCheckRollup,title,url 2>/dev/null || echo "no PR found"
  • Review comments: !gh pr view $ARGUMENTS --json comments,reviews 2>/dev/null || gh pr view --json comments,reviews 2>/dev/null || echo ""
  • CI checks: !gh pr checks $ARGUMENTS 2>/dev/null || gh pr checks 2>/dev/null || echo ""

Task

Using the live state above, produce a merge-readiness report.

  1. State: open / closed / merged / draft.
  2. CI: all green, or list failing checks with names and conclusions.
  3. Reviews: approved / changes-requested / pending. Summarize any unaddressed review comments.
  4. Merge readiness: mergeStateStatus interpretation -- CLEAN, BEHIND (needs rebase), BLOCKED (required checks), DIRTY (conflicts), UNSTABLE (non-required failures).
  5. If CI is failing, fetch the failing run's log head and identify the root cause (test failure, lint, build error). Suggest a narrow fix.

Output

PR: <title> (#<num>)
State: <state>
CI: <all-green | N failing: ...>
Reviews: <status>
Merge: <ready | blocked: <reason>>
Action: <one line>

$ARGUMENTS

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. 3d ago Changed d88e9e2523b5
  2. 10d ago First seen · 35 lines · 14 tokens per session scan A 9421168be370

Subscribe to this mod's changes

check-pr is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 407 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.

Claude CodeCode reviewGit and workflowai-agentsclaudedeveloper-toolsmarketplaceplugins
Related

Other commands, from other repositories

commit

Create a git commit with intelligent message drafting (-f for fast, -v for verbose).

shrwnsan/vibekit-claude-plugins · 18 tokens

review-arch

Review app architecture: components, data flows, risks, and prioritized improvements.

shrwnsan/vibekit-claude-plugins · 0 tokens

resolve-pr

Resolve PR review feedback — fetch unresolved threads, triage, dispatch resolver agents, reply + resolve via GraphQL.

gmickel/flow-next · 26 tokens

pr

Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.

azrtydxb/procoder · 20 tokens

status

The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.

azrtydxb/procoder · 23 tokens

fix-comments

Address PR review comments by implementing requested changes automatically.

rohitg00/awesome-claude-code-toolkit · 13 tokens