Rjv pr descriptions
npx -y skills add rjvim/ai-skills --skill rjv-pr-descriptionsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when writing, generating, updating, or fixing a GitHub PR description. Applies the Current-way/New-way + What-To-Test format; on update preserves checked checkboxes + author content; posts the result.
SKILL.md
2.6 KB, as published. Nobody here has run it
PR Descriptions
Format
One section per logical change:
## Change N: <Short Title>
Current way: <one sentence — what happens today>.
New way: <one sentence — what happens after this PR>.
### What To Test
- [ ] <Action verb: Create / Open / Submit / Uncheck…>
- [ ] Confirm <observable outcome>.
- [ ] <Edge case setup>
- [ ] Confirm <edge case outcome>.
Rules:
- "Current way / New way" — plain English, user-facing behavior only. No code, no implementation details.
- Test steps start with an action verb. Confirm steps start with "Confirm".
- Cover happy path + key edge cases. Not exhaustive — just the combinations that matter.
- No filler. No "Overview" or "Summary" headers. Jump straight to the changes.
- No AI signature, attribution, or generator footer (
Generated by Claude,Generated by Codex, model names, badges, or equivalents) unless the human explicitly asks for it.
Workflow
Writing a new description
- Read the actual diff:
gh pr diff <number>. For context (title, commits, existing body):gh pr view <number> --json title,commits,body. - Identify logical changes (one section per change).
- Write sections in the format above.
- Post:
gh pr edit <number> --body-file -(pipe the body in; inline--bodybreaks on multi-line/special chars).
Updating an existing description
- Fetch current body first:
gh pr view <number> --json body - Preserve all
- [x]checked checkboxes — never uncheck or remove them. - Preserve any content manually added by author/reviewer outside the generated format.
- Merge in new changes — add new
## Change Nsections, append new test steps. - Only replace content you explicitly generated in a prior run.
- Remove AI-attribution text generated by a prior agent run; it is generated content, not manually authored content. Do not remove deliberate human attribution.
- Post the merged result back.
Adding Images
To embed a screenshot or before/after image:
- Produce the image — via your browser-automation tool (e.g.
agent-browser screenshoton the running app; check the project's docs for local login sequences), or use an image the user provides. - Pass the absolute path to the
rjv-github-image-uploadskill — it returns agithub.com/user-attachmentsURL ready to paste inline (private-repo images stay private).