borghei/Claude-Skills / engineering/pr-description-writer
pr-description-writer
VerifiedWrite PR descriptions with evidence, verification steps and a one-way/two-way merge-risk call. Use when opening a PR, when asked to write or fix a PR body, or when checking a description before requesting review.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| assets/pr-body-template.md | markdown | 1.3 KB |
| assets/sample_changed_files.json | config | 419 B |
| assets/sample_migration.diff | other | 990 B |
| assets/sample_pr_body_flawed.md | markdown | 604 B |
| assets/sample_pr_body_good.md | markdown | 2.3 KB |
| references/merge-risk-classification.md | markdown | 6.7 KB |
| references/pr-body-anatomy.md | markdown | 6.3 KB |
| scripts/pr_body_lint.pyexecutable | script | 12.3 KB |
| scripts/risk_classifier.pyexecutable | script | 12.1 KB |
assets/pr-body-template.md
View on GitHub<!--
PR body template. Delete every comment before opening the PR; pr_body_lint.py
warns on leftovers. Keep the whole body under ~400 words: link out for detail.
-->
## Summary
<!-- One or two sentences: what changes for whom. Then, only if it saves reading,
ONE small picture: a diff-sketch of the shape, a call tree, a file tree, or a
mermaid sequence diagram. Pick the smallest view that makes the point. -->
## Why
<!-- The problem in the user's or operator's terms, plus the ticket link.
"BILL-412" alone is not a why. -->
## Evidence
<!-- Before and after, strongest available tier first:
screenshot or recording (UI) > test or command output (behaviour) > CI/staging run link > metrics.
Redact tokens, cookies, emails and customer IDs from anything pasted. -->
**Before:**
**After:**
## How to verify
<!-- Numbered steps a reviewer can repeat in under 10 minutes, with exact commands
and the expected result of each. "Tested locally" is not a step. -->
1.
2.
3.
## Merge risk
<!-- Door: two-way (revert is a full rollback) or one-way (revert does not undo
it: migrations, public API/contract changes, persisted formats, data deletion,
external side effects). Run scripts/risk_classifier.py --emit-section for a draft. -->
**Classification:**
**Blast radius:**
**Rollback plan:**
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |