lambdalisue/pr-update
home/claude/skills/pr-update/SKILL.md
Update the title and body of an existing pull request
$ install --global
skillsauthnpx skillsauth add lambdalisue/dotfiles pr-updateInstall 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 15, 2026, 1:19 PM11.5s1 file scanned
SKILL.md
- name:
- pr-update
- allowed-tools:
- Bash(git branch:*), Bash(git log:*), Bash(git diff:*), Bash(gh pr:*), AskUserQuestion
- argument-hint:
- [PR_NUMBER] Optional PR number to update
- description:
- Update the title and body of an existing pull request
Context
!git branch --show-current
!gh pr view --json number,title,body,baseRefName,headRefName --jq '"\(.number) \(.headRefName) -> \(.baseRefName)\nTitle: \(.title)\nBody:\n\(.body)"' 2>/dev/null || echo "No PR found for current branch"
Principles
Target PR:
- If PR number is provided as argument, use that PR
- Otherwise, find PR associated with current branch via
gh pr view
Language: Match the language of the existing PR title and body. Default to English if unclear.
Scope: Use only origin/<base>..HEAD diff for analysis.
Title: Concise summary of all changes (imperative mood)
Body: Explain WHY these changes were made, not just WHAT changed. Preserve existing structure if the body already follows a consistent format.
Workflow
-
Identify PR - Determine target PR number:
- If argument provided: use that PR number
- Otherwise: run
gh pr view --json number --jq '.number'to get PR for current branch
-
Fetch Current PR - Get current title, body, and base branch:
gh pr view <number> --json title,body,baseRefName,headRefName -
Analyze Changes - Review commits and diffs from base branch:
git log --oneline origin/<base>..HEAD git diff --stat origin/<base>..HEAD -
Detect Language - Check the language of the existing PR title/body
-
Draft Update - Create updated title and body, displayed in a fenced code block:
Title: <concise summary> ## Summary - <bullet points of changes> ## Why <explanation of WHY these changes were made> ## Test Plan - [ ] <test items> -
Show Diff - Clearly show what changed from the current PR:
- Current title → New title
- Summarize body changes
-
STOP - Wait for user approval before updating (use AskUserQuestion)
-
Update - Only after user confirms, execute:
gh pr edit <number> --title "<title>" --body "<body>"
Example Output
### Current
Title: Add new feature
### Proposed
Title: Add OAuth2 support for GitHub login
## Summary
- Add GitHub OAuth2 authentication flow
- Store tokens securely with encryption
## Why
Users requested GitHub login to avoid creating separate accounts.
OAuth2 chosen over OAuth1 for simpler flow and short-lived tokens.
## Test Plan
- [ ] Test login flow with valid GitHub account
- [ ] Verify token refresh works correctly
Begin
Identify the target PR (from argument or current branch), fetch current title and body, analyze commits, and draft updated content for user approval.
IMPORTANT:
- After drafting the updated PR content, you MUST ask the user for approval using AskUserQuestion before updating the PR
- Show clearly what will change (current vs proposed)
- Pass the body via a HEREDOC to
gh pr editto preserve formatting
Related Skills
lambdalisue/pr-update-now
tools
VerifiedTrustedCommunity
Update the title and body of an existing pull request WITHOUT asking for approval
41SKILL.mdUpdated May 30, 2026
lambdalisue/pr-create-now
tools
VerifiedTrustedCommunity
Create a pull request with title and body based on commits WITHOUT asking for approval
41SKILL.mdUpdated May 30, 2026
lambdalisue/git-commit-staged-now
tools
VerifiedTrustedCommunity
Create a Conventional Commit from already staged changes WITHOUT asking for approval
41SKILL.mdUpdated May 30, 2026
lambdalisue/git-commit-staged-fixup-now
tools
VerifiedTrustedCommunity
Map staged changes to existing commits and create fixup commits for autosquash WITHOUT asking for approval
41SKILL.mdUpdated May 30, 2026