pr-review-loop

A set of instructions for following a GitHub pull request review loop before merging. A pull request is a proposed code change that others review on GitHub.

In plain words
What is it for?
Use it when preparing to merge, squash-merge, or auto-merge a pull request, monitoring review comments, addressing feedback, or waiting for approval.
Why use it?
It helps ensure review comments are handled and required approval is present before the change is merged. It also covers cases such as marking a pull request ready or enabling automatic merging.

Skill for Claude CodeCodex

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/basicmachines-co/basic-memory/pr-review-loop
Any agent
npx skills add basicmachines-co/basic-memory --skill pr-review-loop
Clone the repo
git clone --depth 1 https://github.com/basicmachines-co/basic-memory

Made for: Claude Code, Codex.

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,074 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00092 $0.03074
Opus 5 $0.00046 $0.01537
Sonnet 5 $0.00018 $0.00615
Haiku 4.5 $0.00009 $0.00307

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

Security

Grade A, and why

pr-review-loop 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.

.agents/skills/pr-review-loop/SKILL.md · 308 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 308 lines · 92 tokens per session scan A 60a2c4452cd8

Subscribe to this mod's changes

pr-review-loop is a skill published in the GitHub repository basicmachines-co/basic-memory (3,804 stars, last pushed yesterday), licensed AGPL-3.0. It adds 92 tokens to every session and 3,074 once invoked, about $0.0005 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-30.

Related

Other skills, from other repositories

review-pr

Review a Dograh pull request, branch diff, or pasted patch for repo-specific security and correctness risks that are not obvious from generic FastAPI, Next.js, or Python conventions. Use when the user asks to review a PR, audit a diff, check whether changes are safe to merge, review their own changes, or asks what to…

dograh-hq/dograh · 109 tokens

review-agents-md

Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.

dograh-hq/dograh · 82 tokens

merge-pipecat-upstream

Merge the latest upstream pipecat-ai/pipecat tag into the pipecat submodule fork (dograh-hq/pipecat) and bump the dograh repo to it. Use whenever the user asks to bump, upgrade, sync, or merge pipecat, resolve pipecat merge conflicts, audit whether upstream changes break or supersede Dograh's in-fork patches, or…

dograh-hq/dograh · 102 tokens

cli-commands

MUST use when using the CLI, including debugging job failures and inspecting run history via wmill job.

windmill-labs/windmill · 26 tokens

native-trigger

Guidance for adding native trigger services to Windmill. Use when implementing or modifying native trigger integrations across the backend and frontend.

windmill-labs/windmill · 28 tokens

write-script-bun

MUST use when writing TypeScript scripts. Bun is the default and preferred TypeScript runtime — pick it for TypeScript unless the script specifically needs Deno.

windmill-labs/windmill · 37 tokens