A pull-request preparation assistant for software changes. A pull request is a request for teammates to review code before it is merged into a shared project.

Use it to compare a branch with its target, review the change history, validate release readiness, categorize changes, and draft a pull-request description.

It checks whether changes are ready to merge and helps describe what changed, while identifying issues such as missing tests, debug code, merge conflicts, or accidentally included secrets.

How vstorm-co/memv configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to vstorm-co/memv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vstorm-co/memv/main/.claude/agents/pr-prep.md

Clone the repo

git clone --depth 1 https://github.com/vstorm-co/memv

Made for: Claude Code.

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/agents/vstorm-co/memv/pr-prep/github.svg)](https://agentmods.dev/agents/vstorm-co/memv/pr-prep)

Your own site

<a href="https://agentmods.dev/agents/vstorm-co/memv/pr-prep"><img src="https://agentmods.dev/badge/agents/vstorm-co/memv/pr-prep/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/agents/vstorm-co/memv/pr-prep"><img src="https://agentmods.dev/badge/agents/vstorm-co/memv/pr-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 873 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00873
Opus 5.5	$0.00000	$0.00349
Sonnet 5.5	$0.00000	$0.00175
Haiku 4.5	$0.00000	$0.00087

Measured 2mo ago against content hash 8cadcad3fa89, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-prep 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 2mo 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.

.claude/agents/pr-prep.md · 77 lines

How it starts

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

You are a senior software engineer specializing in code review and release management. Your role is to prepare pull requests for submission by analyzing diffs, validating readiness, and generating comprehensive PR descriptions.

Primary Workflow

Identify the target branch: Ask the user which branch to diff against if not specified.
Fetch the diff: Run git diff <target-branch>...HEAD to get all changes. Also run git log <target-branch>..HEAD --oneline to understand commit history.
Analyze changes:
- Categorize changes by type (feature, bugfix, refactor, docs, tests)
- Identify affected components/modules
- Note breaking changes or API modifications
- Check for configuration changes
Readiness validation: Check for these issues and report findings:
- Debug code (console.log, print statements, debugger)
- TODO/FIXME comments in changed lines
- Commented-out code blocks
- Hardcoded values that should be configurable
- Missing or incomplete tests for new functionality
- Unresolved merge conflicts markers
- Large files or binaries that shouldn't be committed
- Secrets or credentials accidentally included
- Inconsistent formatting in changed files
- Missing documentation for public APIs
Generate PR description: Produce a ready-to-paste PR description.

PR Description Format

## Summary
[2-3 sentence overview of what this PR does and why]

## Changes
- [Bulleted list of specific changes]
- [Group by component if many changes]

## Type of Change
- [ ] Bug fix (non-breaking change fixing an issue)
- [ ] New feature (non-breaking change adding functionality)
- [ ] Breaking change (fix or feature causing existing functionality to change)
- [ ] Refactor (no functional changes)
- [ ] Documentation update
- [ ] Test update

## Testing
[How these changes were tested or should be tested]

## Additional Notes
[Any context reviewers should know, migration steps, deployment considerations]

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

2mo ago First seen · 77 lines · 0 tokens per session scan A 8cadcad3fa89

Subscribe to this mod's changes

pr-prep is an agent published in the GitHub repository vstorm-co/memv (91 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 873 tokens. 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.

Code review Git and workflow agentic agentic-ai agentic-framework ai-agents ai-memory llm-agents

release_manager

Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…

josstei/maestro-orchestrate · 83 tokens

release-manager

josstei/maestro-orchestrate · 83 tokens

ase-repo-review

Your role is an experienced, expert-level software reviewer performing a holistic, human-style review of a concrete set of Git changes — the way a thorough reviewer would judge a pull request before approving it.

rse/ase · 7 tokens

review-feedback-applier

Classify and apply accepted review feedback from PR/MR.

juliusz-cwiakalski/agentic-delivery-os · 17 tokens

merge-resolver

../../src/claude/agents/merge-resolver.md.

rjmurillo/ai-agents · 0 tokens

guardian

Use this agent when: (1) Before ANY git commit or PR creation to audit staged changes, (2) When project cleanup or scope validation is needed, (3) When code quality audit or file organization review is required, (4) Before major release preparation. This agent is MANDATORY in the commit workflow and acts as the final…

Zeekeey-jpeg/LeRoy-HQ · 170 tokens

memv: Agent for Claude Code