lwlee2608/gh-update-pr
skills/gh-update-pr/SKILL.md
Use when updating GitHub PR title or body. Works around the gh pr edit GraphQL bug caused by GitHub's Projects Classic deprecation.
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add lwlee2608/agent-skills gh-update-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 16, 2026, 7:11 AM20.2s1 file scanned
SKILL.md
- name:
- gh-update-pr
- description:
- Use when updating GitHub PR title or body. Works around the gh pr edit GraphQL bug caused by GitHub's Projects Classic deprecation.
- user-invocable:
- true
Update PR via REST API
gh pr edit is broken due to GitHub deprecating Projects Classic (projectCards GraphQL field error). Use the REST API instead. gh pr view and gh pr create still work fine — only gh pr edit is affected.
Rules
- Never use
gh pr editto update PR title or body. It will fail with a GraphQL error. - Use
gh apiwith the REST endpoint. Always pipe JSON viajq --argto avoid shell injection:jq -n --arg title "..." --arg body "..." '{title: $title, body: $body}' | \ gh api repos/{owner}/{repo}/pulls/{number} -X PATCH --input - --jq '.html_url' - Get the current PR context before updating:
gh pr view --json number,url,baseRefName - Omit unchanged fields. If only updating the title, do not include
bodyin the JSON payload, and vice versa. Including an unchanged field risks overwriting it with stale content.
Verification procedure
- After the PATCH request, confirm it returned the PR's
html_url(not an error). - Run
gh pr view --json title,bodyand verify the updated fields match what was intended.
Common mistakes to watch for
- Including both title and body when only one changed. This can overwrite the other field with stale or empty content. Only include the field being updated.
- Running outside a git repo with a tracking branch.
gh pr viewneeds repo context. If it fails, pass--repo owner/repoexplicitly. - Forgetting to extract owner/repo/number. Always fetch these from
gh pr viewfirst — do not hardcode or assume them.
Related Skills
lwlee2608/handoff
documentation
VerifiedTrustedCommunity
Use when the user wants to condense the current conversation into a handoff document for another agent to pick up.
SKILL.mdUpdated May 22, 2026
lwlee2608/whiteboard-explain
development
VerifiedTrustedCommunity
Use when the user asks to explain or teach a technical concept. Replies in plain language with a simple diagram instead of a wall of jargon.
SKILL.mdUpdated May 18, 2026
lwlee2608/writing-system-prompts
development
VerifiedTrustedCommunity
Use when writing or editing a system prompt for any LLM API or SDK (any code passing a `system=` / `system` role parameter, or a `.txt`/`.md` file holding such a prompt). Applies prompt-engineering and prompt-caching best practices.
SKILL.mdUpdated May 13, 2026
lwlee2608/prefer-make
tools
VerifiedTrustedCommunity
Use before running any Go toolchain command (`go build`, `go test`, `go run`, `go vet`, `go fmt`, `golangci-lint`). Substitutes make targets when a Makefile is present.
SKILL.mdUpdated Apr 16, 2026