analyze-prs

analyze-prs is a skill for Claude Code from TalonT-Org/AutoSkillit. It costs 45 tokens per session (4,597 once invoked), scanned A, original, MIT.

A pull request (PR) is a proposed code change submitted for review before it is added to a shared branch. This skill examines all open PRs aimed at a chosen base branch.

In plain words
What is it for?
Use it at the start of a PR consolidation workflow to find a safe merge order and label each PR as simple or needing a check.
Why use it?
It helps prevent unsafe merge sequences by showing which changes overlap, which are blocked, and which need closer review.

Skill for Claude Code

Written for Claude Code: hooks in frontmatter. Also seen: mentions subagents.

Part of the autoskillit plugin — 121 skills, 1 MCP server shipped together

Good fit Use it at the start of a PR consolidation workflow to find a safe merge order and label each PR as simple or needing a check.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/talont-org/autoskillit/analyze-prs
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.

Any agent
npx skills add TalonT-Org/AutoSkillit --skill analyze-prs
Clone the repo
git clone --depth 1 https://github.com/TalonT-Org/AutoSkillit

Made for: Claude Code.

Or install autoskillit, the plugin that ships this one along with the rest of its 121 skills, 1 MCP server.

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 analyze-prs

README.md
[![agentmods](https://agentmods.dev/badge/skills/talont-org/autoskillit/analyze-prs.svg)](https://agentmods.dev/skills/talont-org/autoskillit/analyze-prs)
Your own site
<a href="https://agentmods.dev/skills/talont-org/autoskillit/analyze-prs"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/analyze-prs.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,597 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.00045 $0.04597
Opus 5 $0.00023 $0.02299
Sonnet 5 $0.00009 $0.00919
Haiku 4.5 $0.00005 $0.00460

Measured 7d ago against content hash 3002667e166d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

analyze-prs 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 7d 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.

src/autoskillit/skills_extended/analyze-prs/SKILL.md · 433 lines

How it starts

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

PR Analysis Skill

Analyze all open PRs targeting a base branch, determine a safe merge order, assess complexity, and produce machine-readable output for the merge-prs recipe.

When to Use

  • At the start of a merge-prs run
  • User wants to understand which PRs can be merged safely and in what order
  • User says "analyze PRs", "order PRs", or "assess PR complexity"

Critical Constraints

NEVER:

  • Merge, close, or modify any PR
  • Modify any source code files
  • Create files outside {{AUTOSKILLIT_TEMP}}/merge-prs/ directory
  • Run subagents in the background (run_in_background: true is prohibited)

ALWAYS:

  • Use subagents to fetch PR data in parallel
  • Use model: "sonnet" when spawning all subagents via the Task tool
  • Abort clearly if gh CLI is not authenticated
  • Include every open PR targeting base_branch in the output — no PR is silently dropped (blocked PRs appear in ci_blocked_prs / review_blocked_prs arrays, not in the ordered prs list)
  • Default to parallel batch processing: When multiple PRs are present, ALWAYS process all analysis tasks (diff fetching, overlap computation, complexity tagging) using parallel subagent batches. Processing PRs one-at-a-time without an explicit user instruction to do so is the wrong default. Up to 8 PRs should be processed in a single parallel batch; launch additional batches for larger sets.

Arguments

{base_branch} [merge_queue_data_path=<path>]

  • base_branch — the base branch to list PRs against (e.g., main)
  • merge_queue_data_path (optional) — absolute path to a JSON file containing pre-fetched merge queue data (produced by fetch_merge_queue_data run_python step). When provided and present, read from file instead of calling GitHub GraphQL API inline.

Workflow

Step 0: Authenticate and List PRs

Run:

gh pr list --base {base_branch} --state open --json number,title,headRefName,author,body,additions,deletions,changedFiles --limit 100

If zero PRs are returned: write a summary to terminal and exit cleanly with an empty pr_order_{ts}.json (zero PRs, no integration branch needed).

Read the full file on GitHub · 433 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. 7d ago First seen · 433 lines · 45 tokens per session scan A 3002667e166d

Subscribe to this mod's changes

analyze-prs is a skill published in the GitHub repository TalonT-Org/AutoSkillit (5 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 4,597 once invoked, about $0.0002 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.