An automated pull-request check for GitHub, a service for hosting code and reviewing changes. It follows the automated tests attached to a pull request and shows review comments that still need attention.

Use it after pushing a branch to find its pull request, monitor continuous-integration checks, and list unresolved reviewer comments. It can also show review comments without waiting for the checks.

It saves you from repeatedly checking whether tests finished or searching through review discussions after pushing code. When checks fail, it points to the relevant run so you can investigate.

check-pr — Skill by kolodkin

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 skills/kolodkin/devpowers/check-pr

Any agent

npx skills add kolodkin/devpowers --skill check-pr

Clone the repo

git clone --depth 1 https://github.com/kolodkin/devpowers

Made for: Claude Code, Codex.

Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,336 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 2 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.

Model	Per session	Once invoked
Fable 5	$0.00112	$0.02336
Opus 5	$0.00056	$0.01168
Sonnet 5	$0.00022	$0.00467
Haiku 4.5	$0.00011	$0.00234

Measured 2d ago against content hash 0c94d799ec23, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

check-pr scanned grade B with 2 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

`get_job_logs` comes from the actions toolset, enabled by the `X-MCP-Toolsets: all` header in the plugin's bundled `.mcp.json`. If it isn't in your tool list, the plugin's `github` MCP didn't load — see Step 0. One-off f

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Call `mcp__plugin_devpowers_github__get_job_logs` with `owner`, `repo`, `job_id: <external_id>`, `return_content: true`, and `tail_lines: 30`. It returns the tail of the job log directly — no curl, no `gh`. (It also acce

skills/check-pr/SKILL.md · 159 lines

How it starts

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

PR Check Skill

You are a PROACTIVE GitHub PR assistant. After EVERY git push, automatically run this skill to verify CI and surface any unresolved review comments. If checks fail, triage them; if reviewers asked for changes, address the threads.

Invocation

/check-pr                  # full flow: PR lookup → CI watch → review comments
/check-pr --comments-only  # skip CI watch, only surface unresolved review threads

Step 0 — Ensure GitHub MCP is available

This skill drives everything through the mcp__plugin_devpowers_github__* tools — the github MCP server bundled with this plugin (its .mcp.json).

If mcp__plugin_devpowers_github__list_pull_requests is visible in your tool list, proceed.
If it's missing, the plugin's bundled github MCP didn't connect — almost always because GH_TOKEN isn't set (it authenticates with Bearer ${GH_TOKEN}). Tell the user to export GH_TOKEN=<pat> (a long-lived PAT) and restart Claude Code (or run /reload-plugins), then re-invoke /check-pr. Stop until the server loads.

Step 1 — Resolve repo and branch

Two cheap shell commands:

git remote get-url origin
git rev-parse --abbrev-ref HEAD

Parse owner/repo from the remote URL. Accept github.com[:/]<owner>/<repo>(.git) and proxied /git/<owner>/<repo> forms. If parsing fails, surface the remote URL to the user and stop — don't guess.

Step 2 — Find the PR for this branch

Call mcp__plugin_devpowers_github__list_pull_requests with owner, repo, state: "open", and head: "<owner>:<branch>". If the result is empty, tell the user no PR is open for <branch> — for branches that don't target main/master directly, no PR means no CI. Offer to create one with mcp__plugin_devpowers_github__create_pull_request only if the user explicitly asks; otherwise stop.

If multiple PRs come back (rare), pick the most recently updated and note the others.

Cache the PR number (<pr>) for the rest of the run.

Step 3 — Check review comments

Read the full file on GitHub · 159 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.

2d ago First seen · 159 lines · 112 tokens per session scan B 0c94d799ec23

Subscribe to this mod's changes

check-pr is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 23d ago), licensed MIT. It adds 112 tokens to every session and 2,336 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Git and workflow Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

check-pr