stevenmburns/rename-pr
skills/rename-pr/SKILL.md
Analyze the changes in the current PR and suggest a more accurate title if the current one no longer fits
tools
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add stevenmburns/dot-claude-files rename-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 4:34 AM16.1s1 file scanned
SKILL.md
- name:
- rename-pr
- description:
- Analyze the changes in the current PR and suggest a more accurate title if the current one no longer fits
- user-invocable:
- true
- allowed-tools:
- Bash
Rename PR
Analyze the current PR's changes and evaluate whether the title still accurately describes what is being done.
Steps
- Run
gh pr view --json number,title,bodyto get the current PR title and description - Run
git log main..HEAD --onelineandgit diff main...HEAD --statto understand the full scope of changes - Compare the changes to the current title:
- Does the title accurately reflect the nature and scope of the changes?
- Has the work drifted significantly from what the title implies?
- Is the title too narrow, too broad, or misleading given what was actually done?
- Based on your analysis:
- If a better title is warranted: propose a specific new title (under 70 chars, conventional style matching the existing title's casing/format) and explain concisely why it's more accurate
- If the current title is still appropriate: explain why it still fits and make no change
- If you proposed a new title, ask the user to confirm before applying it. Accept yes/no or a user-provided alternative title.
- If confirmed, run
gh pr edit --title "<new title>"and report the updated title.
Related Skills
stevenmburns/triage-issues
tools
VerifiedTrustedCommunity
Scan open GitHub issues, flag duplicates, and summarize with suggested priorities
SKILL.mdUpdated Apr 20, 2026
stevenmburns/tidy-branch
testing
VerifiedTrustedCommunity
Interactively clean up the current branch's commits (squash fixups, reword sloppy messages, reorder, drop) before merging — especially important on repos using rebase-merge where every branch commit lands on main verbatim
SKILL.mdUpdated Apr 20, 2026
stevenmburns/merge-pr
data-ai
VerifiedTrustedCommunity
Merge the open PR for the current branch into main, delete the branch, and pull main
SKILL.mdUpdated Apr 20, 2026
stevenmburns/fresh-clone
development
VerifiedTrustedCommunity
Clone the current repo into a sibling directory with a fresh Python venv
SKILL.mdUpdated Apr 20, 2026