What is pr-preparation?

A checklist for preparing a pull request, which is a proposed code change submitted for review. It covers code quality, tests, translations, and self-review.

Use it before submitting changes to check acceptance criteria, run linting and tests, verify internationalization, review code quality, and assemble the pull request.

It catches unfinished work, type or lint errors, missing tests, and user-facing text that is not prepared for translation.

pr-preparation — Cursor rule for Cursor by kubev2v: A checklist for preparing a pull request, which is…

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 rules/kubev2v/forklift-console-plugin/pr-preparation

Clone the repo

git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

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/rules/kubev2v/forklift-console-plugin/pr-preparation.svg)](https://agentmods.dev/rules/kubev2v/forklift-console-plugin/pr-preparation)

Your own site

<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/pr-preparation"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/pr-preparation.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 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.00007	$0.00949
Opus 5	$0.00003	$0.00475
Sonnet 5	$0.00001	$0.00190
Haiku 4.5	$0.00001	$0.00095

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

Security

Grade A, and why

pr-preparation 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 3d 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.

.cursor/rules/workflows/pr-preparation.mdc · 185 lines

How it starts

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

PR Preparation Workflow

Invoke with: "prepare PR", "ready for review", "PR checklist", "before I submit"

Follow this comprehensive workflow before creating a pull request.

1. Code Completion Check

All acceptance criteria met
Edge cases handled
Loading/error/empty states implemented
No TODO comments without linked issues
No commented-out code
No console.log statements
No hardcoded test data

2. Code Quality Checks

Run All Checks

npm run lint && npm test

TypeScript

No type errors
No implicit any types
Explicit return types on functions

Linting

ESLint passes without errors
Prettier formatting applied

Unit Tests

All existing tests pass
New tests added for new code
Edge cases tested

3. i18n Verification

npm run i18n

All user-facing strings use t() function
Translation file changes committed
Proper interpolation for dynamic values

4. Self Code Review

Developer Perspective

Single responsibility followed
Files under 300 lines
No code duplication
No magic numbers
Clean imports (no unused, no barrel files)
Error handling for all async operations

UX Perspective

Loading states visible
Error states informative
Empty states guide users
Keyboard navigation works
PatternFly components used correctly

QE Perspective

Empty/null data handled
Boundary values considered
Double-click prevention where needed
Test coverage adequate

Security Perspective

User input validated
No XSS vulnerabilities
No sensitive data exposed
Permissions checked

5. Visual Verification

Feature works as expected
UI looks correct
Screenshots/video for UI changes (before/after if relevant)

6. Commit Hygiene

Commit Format

All commits must include a Resolves: line and be signed off (-s flag) for DCO compliance:

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

3d ago First seen · 185 lines · 7 tokens per session scan A e3bdac94bfda

Subscribe to this mod's changes

pr-preparation is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 7 tokens to every session and 949 once invoked, about $0.0000 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.

Git and workflow

pr-preparation