What is pull-requests?

A set of instructions for finishing a pull request, the proposed change submitted for review. It covers focused tests, simplification, and a final review of the complete change.

Use it when a change is ready to open, update, or mark ready for review, including continuing an existing pull request.

It helps ensure the request contains only necessary work and that intended behaviour is covered before review. It also checks failure paths, cleanup, comments, and release notes where relevant.

pull-requests — Skill for Claude Code by systemfsoftware

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 systemfsoftware/comment-checker --skill pull-requests

Clone the repo

git clone --depth 1 https://github.com/systemfsoftware/comment-checker

Made for: Claude Code.

Or install comment-checker, the plugin that ships this one along with the rest of its 17 skills, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/systemfsoftware/comment-checker/pull-requests/github.svg)](https://agentmods.dev/skills/systemfsoftware/comment-checker/pull-requests)

Your own site

<a href="https://agentmods.dev/skills/systemfsoftware/comment-checker/pull-requests"><img src="https://agentmods.dev/badge/skills/systemfsoftware/comment-checker/pull-requests/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/systemfsoftware/comment-checker/pull-requests"><img src="https://agentmods.dev/badge/skills/systemfsoftware/comment-checker/pull-requests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 617 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 100% copy Near-identical to another mod 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.1	$0.00034	$0.00617
Opus 5.5	$0.00014	$0.00247
Sonnet 5.5	$0.00007	$0.00123
Haiku 4.5	$0.00003	$0.00062

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

Security

Grade A, and why

pull-requests 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 18d 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.

Origin

This is a copy

100% identical to pull-requests — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

repos/effect/.agents/skills/pull-requests/SKILL.md · 51 lines

What it actually says

A pull request is ready when its tests, implementation, comments, and changeset are each the simplest that cover the intended behavior. Draft PRs can be used earlier; finishing means making the PR ready for review.

Workflow

Run each step in a fresh-context subagent when available; otherwise run it yourself. Pass along the task context and prior results so each step can check its gate.

Keep tests focused. Read test-development for test placement and type. Cover each intended behavior once, in the existing test file for the module. For changes needing no tests, record why. Continue when removing any remaining case would leave intended behavior uncovered, or no tests are needed.
Simplify the implementation. With the tests passing, look for a simpler or more idiomatic version: reuse helpers and patterns from nearby source and effect-development, and remove debugging code, scaffolding, and changes unrelated to the task. Continue when applicable targeted tests pass and every hunk in the diff from the merge base is required by the task.
Review the full diff from the merge base as a maintainer would: correctness, failure and interruption paths, resource cleanup, naming and API consistency with neighboring modules, and documentation. Fix findings and review again. Continue when a review pass produces no findings.
Clean up. Remove comments that restate code or narrate the change; keep the rest short and about why. Finalize the changeset with changesets. Continue when comments explain only what code cannot, and the changeset describes the final consumer impact or the no-changeset reason is recorded.
Run the validation in the AGENTS.md validation table for each change type in the diff. Fix failures caused by the change; if fixes alter the diff, repeat the affected passes. Continue when applicable checks pass or commands that cannot run and their blockers are recorded.
Open or update the pull request. Title: a short imperative summary. Description: the problem addressed, notable decisions, and Closes #<issue> for each GitHub issue resolved. Do not narrate the diff. Mark the PR ready for review. Continue when the final changes are pushed, the description matches the final diff, and the PR is ready for review.

The task is complete when each step's gate holds, validation has passed or been reported as not runnable with reasons, and the pull request is ready for review with a description matching the final diff.

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.

18d ago First seen · 51 lines · 34 tokens per session scan A d291556d75a7

Subscribe to this mod's changes

pull-requests is a skill published in the GitHub repository systemfsoftware/comment-checker (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 617 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pull-requests, differing in 0 lines, and is treated as a copy.

Claude Code Git and workflow ai-agents anthropic ast claude claude-code-hooks

pull-requests next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pull-requestssystemfsoftware/comment-checker	Skill	5	2d ago	Apache-2.0	A	34	Claude Code
diff-projectluiseiman/dotforge	Skill	8	2d ago	MIT	A	25	Claude Code
releaseEdmonds-Commerce-Limited/claude-code-hooks-daemon	Skill	4	yesterday	MIT	A	22	Claude Code
issue-sdlcEdmonds-Commerce-Limited/claude-code-hooks-daemon	Skill	4	yesterday	MIT	A	62	Claude Code
terminalDojoCodingLabs/code-sensei	Skill	14	1mo ago	MIT	A	31	Claude Code
branch-recapMalo-T/claude-toolbelt	Skill	2	1mo ago	MIT	A	338	Claude Code
slack-changelogMalo-T/claude-toolbelt	Skill	2	1mo ago	MIT	A	332	Claude Code