lambdalisue/pr-update-now
home/claude/skills/pr-update-now/SKILL.md
Update the title and body of an existing pull request WITHOUT asking for approval
$ install --global
skillsauthnpx skillsauth add lambdalisue/dotfiles pr-update-nowInstall 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: May 30, 2026, 7:35 AM121.0s1 file scanned
SKILL.md
- name:
- pr-update-now
- allowed-tools:
- Bash(git branch:*), Bash(git log:*), Bash(git diff:*), Bash(gh pr:*)
- argument-hint:
- [PR_NUMBER] Optional PR number to update
- description:
- Update the title and body of an existing pull request WITHOUT asking for approval
When to use
This is the non-interactive variant of /pr-update. The user invoking /pr-update-now IS the explicit intent to update the PR — do NOT ask for approval. Use the interactive /pr-update when the user wants to review the draft first.
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.
Line breaks: Do NOT insert hard line breaks in the middle of a sentence or paragraph. Write each paragraph as a single continuous line and let the renderer wrap it. Only break between paragraphs (blank line), at list items, or at headings. Never hard-wrap to a fixed column width.
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 - If no PR exists for the current branch, report it and STOP immediately.
-
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:
Title: <concise summary> ## Summary - <bullet points of changes> ## Why <explanation of WHY these changes were made> ## Test Plan - [ ] <test items> -
Update - Execute immediately, without asking for approval (the
/pr-update-nowinvocation is the explicit permission). Pass the body via a HEREDOC to preserve formatting:gh pr edit <number> --title "<title>" --body "<body>"Present the PR URL to the user.
Begin
Identify the target PR (from argument or current branch), fetch current title and body, analyze commits, draft updated content, and update the PR immediately. Do NOT ask for approval — the /pr-update-now invocation is the explicit permission.
Related Skills
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
lambdalisue/git-commit-now
tools
VerifiedTrustedCommunity
Analyze working tree changes and commit them WITHOUT asking for approval — fixup into existing commits where appropriate, otherwise new atomic commits
41SKILL.mdUpdated May 30, 2026