From claude-resources
Updates GitHub PR title and body to reflect full implementation after additional commits. Analyzes complete diff from base branch, drafts summary with changes and test plan, confirms with user before applying via gh pr edit.
npx claudepluginhub takazudo/claude-resourcesThis skill uses the workspace's default tool permissions.
Update an existing PR's title and description to accurately reflect the full implementation, not just the original scope.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Update an existing PR's title and description to accurately reflect the full implementation, not just the original scope.
# Get current branch
BRANCH=$(git branch --show-current)
# Fetch latest
git fetch origin
# Get PR details
gh pr view "$BRANCH" --json number,title,body,baseRefName,headRefName
Record the PR number, current title, current body, and base branch.
Review ALL changes in the PR — not just recent commits:
BASE_BRANCH=<baseRefName from step 1>
# All commits in the PR
git log "origin/$BASE_BRANCH".."$BRANCH" --oneline
# Full diff stat
git diff "origin/$BASE_BRANCH"..."$BRANCH" --stat
# Full diff for understanding
git diff "origin/$BASE_BRANCH"..."$BRANCH"
Read the diff carefully. Understand:
Optional: Copilot-assisted body draft
Before drafting manually, attempt to get a Copilot-drafted body:
BASE_BRANCH=<baseRefName from step 1>
DRAFT=$($HOME/.claude/skills/gco/scripts/gco-pr-body.sh "$BASE_BRANCH" 2>/dev/null || true)
If $DRAFT is non-empty, use it as the starting point for the body. Claude must still review and adjust it — fill any gaps, fix inaccuracies, and ensure tone/completeness. If the script fails or returns empty, draft directly as below.
Based on the full diff analysis:
Title: Write a concise PR title (under 70 chars) that captures the overall scope. If the PR covers multiple concerns, summarize the primary theme.
Description: Write a comprehensive PR body using this format:
## Summary
<2-4 bullet points covering the main changes>
## Changes
<Detailed list of what was done, grouped by category if needed>
## Test Plan
<How to verify the changes work correctly>
If the original body contained issue references (e.g., Closes #123, Fixes #456), preserve them in the new body.
Present the proposed updates clearly:
Current title: <old title>
New title: <new title>
Current body:
<old body>
New body:
<new body>
Ask the user to confirm before applying.
PR_NUMBER=<number from step 1>
# Update title
gh pr edit "$PR_NUMBER" --title "<new title>"
# Update body
gh pr edit "$PR_NUMBER" --body "$(cat <<'EOF'
<new body content>
EOF
)"
Report the updated PR URL when done.
--stat first to get an overview, then read key files selectivelyDisposition of every pr-* skill regarding the Copilot-draft path:
| Skill | Disposition |
|---|---|
/pr | Adopt (this sub-task) |
/pr-revise | Adopt (this sub-task) |
/pr-complete | Skip — merge/completion workflow, not text generation |
/pr-split | Skip — structural rearrangement, not text generation |
/pr-recreate | Skip — history cleanup, not text generation |
/pr-make-suggestion-edit | Skip — applies code suggestions as edits, different domain |
/pr-make-suggestion-to-pr | Defer — creates new PRs from suggestion edits; future candidate, track in a follow-up issue |