Menu
Generate a PR description as a Markdown file in .claude/scratch using git history and code analysis. Fills in the project's PR template.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Bump the project version across all files that carry it. Pass the new version as the argument (e.g. /bump-version 0.4.0).
Full code navigation — replaces grep, glob, and file reads. Find symbol definitions, trace callers and callees, read source code, and map module structure. Pass symbol names or questions as arguments.
Diagnose and fix a bug or unexpected behavior. Traces the problem through the dependency graph, adds logging if needed, and proposes a fix. Use when something is broken, producing wrong output, or behaving unexpectedly.
Plan implementation before writing code. Analyzes codebase structure and dependencies, asks clarifying questions, and writes a scoped implementation spec.
| name | gen-pr |
| description | Generate a PR description as a Markdown file in .claude/scratch using git history and code analysis. Fills in the project's PR template. |
| argument-hint | [{"optional":"brief hint about what this PR does"}] |
| allowed-tools | Bash Skill Write |
Generate a PR description for the current branch. $ARGUMENTS
Step 1 — Gather git context (read-only)
Run these git commands in parallel to understand what changed:
git log main..HEAD --oneline — list commits on this branchgit diff main..HEAD --stat — files changed and line countsgit diff main..HEAD -- '*.rs' '*.py' '*.ts' '*.tsx' — full diff for source files (skip lock files, build artifacts)Do NOT run any git command that writes, stages, or modifies state.
Step 2 — Analyze changed symbols
From the diff, identify the key symbols that were added or modified (functions, classes, types, components). Run a single /code-analysis call with the most important ones (comma-separated) to understand:
Do not read files directly. Use source blocks from the analysis.
Step 3 — Write the PR description
Write the completed PR description to .claude/scratch/pr-[branch-name].md in the project root, filling in the template below. Use only what you know — do not invent testing steps or checklist items you can't verify from the diff and analysis.
Template to fill in:
## Summary
[1–3 sentences: what this PR does and why. Be specific — name the symbols, modules, or behaviors changed.]
## Changes
- [one bullet per logical change; reference file paths or symbol names where useful]
- ...
## Testing
[Describe what was actually changed and how a reviewer would verify it. Name specific commands, flags, or behaviors to check. If the change is Rust-only CLI/lib work, note that; if it touches the frontend, mention what to look at in the browser.]
## Checklist
- [ ] Rust changes: `cargo clippy` passes
- [ ] TypeScript changes: `npx tsc --noEmit` passes in `frontend/`
- [ ] Python changes: type annotations added to any new functions
- [ ] Tested end-to-end with `serpentine serve`
Only check a checklist item if the diff confirms no changes in that area (e.g. no .rs files changed → Rust item is not relevant, omit it) or if you can verify compliance from the diff itself. Leave items unchecked when in doubt.
Step 4 — Report
Tell me the path to the generated file and give a one-paragraph summary of what you wrote so I can decide whether to use it as-is or ask for edits.