← Cursor Slash Commands · ENGINEERING
/pr-description
Generate PR Descriptions from Your Diff
Reads the diff against main and writes summary, risk, test plan and a screenshots checklist.
/pr-description Solo founder variant, merging to main, add rollback and post-deploy watch listWhere it installs
# .cursor/commands/pr-description.md
# no frontmatter, the file opens with its H1 title# .claude/commands/pr-description.md
---
description: ...
argument-hint: [optional: base branch or solo-founder variant]
allowed-tools: Read, Grep, Glob, Write, Bash(git status:*), Bash(git diff:*), ...
---What it does
/pr-description is a Cursor slash command. Type it in chat to run a saved workflow: Generate PR Descriptions from Your Diff.
Compares the current branch to main with git diff and writes a pull request description with a summary, grouped changes, ordered risks, a runnable test plan and a screenshots checklist. Includes a solo-founder variant that adds rollback and post-deploy watch items for merging straight to main.
Reads the diff against main and writes summary, risk, test plan and a screenshots checklist. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /pr-description for you.
Why it exists
Founders retype the same multi-step prompt until it rots. /pr-description exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.
It ships in the Engineering Kit. It is wired to the API & Technical Documentation Writer (technical-writer) and Technical Lead & System Architect (tech-lead) agents. Required skills: Technical Documentation & OpenAPI Spec Design; Project Conventions & CURSOR.md Standards.
When to use it
- Use when the branch is ready and the PR description is empty or a one-liner, or when you merge to main alone and want a record of what shipped and what to watch.
- Use /pr-description when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
- Start a new chat. Do not run this command in a thread that just wrote marketing copy.
When not to use it
- Do not run /pr-description as a substitute for reading the diff. The command produces files; you still gate them.
- Do not chain it into a 40-turn chat. Fresh context is part of the design.
- Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.
Example workflow
- Run git status, git log main..HEAD and git diff main...HEAD --stat; stop if the diff is empty
- Read the files that carry the logic and skip lockfiles and generated output
- Write Summary, Changes, Risk (migrations, auth, billing, env vars), Test plan and Screenshots sections
- Save PR_DESCRIPTION.md and print it; offer gh pr create --body-file only when asked
Example usage
Type this in Cursor chat: /pr-description Solo founder variant, merging to main, add rollback and post-deploy watch list
The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.
If a phase fails its gate, stop. Do not add 'just continue'.
Example output
- Expected artifact: PR_DESCRIPTION.md
Best practices
- Keep the prompt specific. /pr-description Solo founder variant, merging to main, add rollback and post-deploy watch list is the shape: object, constraint, and outcome.
- Let the listed agents work in order: technical-writer → tech-lead.
- Save outputs in the repo. Chat-only answers evaporate.
- Engineering commands should leave tests or an audit note, not only implementation files.
Common mistakes
- Typing /pr-description with no object ('do the thing'). The pipeline will guess.
- Re-running the command in the same chat after a failed gate instead of fixing the failing file.
- Editing the command file to skip review so it 'goes faster'.
- Skipping the Technical Documentation & OpenAPI Spec Design skill that the command depends on.
Frequently asked questions
What does /pr-description do in Cursor?
Compares the current branch to main with git diff and writes a pull request description with a summary, grouped changes, ordered risks, a runnable test plan and a screenshots checklist. Includes a solo-founder variant that adds rollback and post-deploy watch items for merging straight to main.When should I run /pr-description?
Use when the branch is ready and the PR description is empty or a one-liner, or when you merge to main alone and want a record of what shipped and what to watch.What is an example /pr-description prompt?
/pr-description Solo founder variant, merging to main, add rollback and post-deploy watch listWhich skills does /pr-description load?
Technical Documentation & OpenAPI Spec Design; Project Conventions & CURSOR.md StandardsIs /pr-description a Cursor skill?
No. /pr-description is a slash command you type. Skills are playbooks the agent may load. Use both: the command runs the workflow, the skills constrain how it writes.
Run /pr-description from your own repo
AgenticKit installs 47 slash commands, 46 agents, and 61 skills. One command installation.