Creates comprehensive PR descriptions by systematically reviewing ALL changes - features, bug fixes, tests, docs, and infrastructure. Use when user wants to update PR description, prepare PR for review, or document branch changes. Requires gh CLI.
Creates comprehensive PR descriptions by systematically reviewing ALL changes - features, bug fixes, tests, docs, and infrastructure. Use when updating PR descriptions or preparing PRs for review. Requires gh CLI.
/plugin marketplace add propstreet/claude-powerpack/plugin install claude-powerpack@propstreetThis skill is limited to using the following tools:
EXAMPLES.mdREADME.mdCreate thorough PR descriptions that document EVERY meaningful change, not just the headline feature.
NEVER assume you know what's in the PR based on branch name or first glance.
PRs often contain:
You MUST systematically review ALL changes and include them in the summary.
First, determine the base branch for comparison. Run these commands separately:
Step 1: Try to get base branch from PR:
gh pr view --json baseRefName -q '.baseRefName' 2>/dev/null
Step 2: If no PR exists (empty output above), get the default branch:
git rev-parse --abbrev-ref origin/HEAD 2>/dev/null | sed 's#origin/##' || echo 'main'
Use the result as BASE_BRANCH for the commands below.
Then gather context. These commands are independent and can be run as separate tool calls:
PR and working tree status:
gh pr status
git status --short
Changed files:
git diff origin/$BASE_BRANCH...HEAD --stat
git diff origin/$BASE_BRANCH...HEAD --name-status
Commit history:
git log origin/$BASE_BRANCH..HEAD --oneline --no-merges
Note: Using the PR's actual base branch ensures accurate diffs for release backports or PRs targeting non-default branches.
Using the --name-status output, create a categorized inventory of EVERY changed file:
*Service*, *Controller*, *Component*)For EACH commit in git log:
Common prefixes:
fix: = bug fix (HIGH PRIORITY - always include)feat: = feature (main work)test: = test infrastructuredocs: = documentationperf: = performance optimizationrefactor: = code organizationchore: = maintenance tasksBefore writing the summary, confirm you've checked:
If you cannot check ALL boxes, you are not done gathering data.
Structure your summary to cover ALL categories of changes.
## Summary
[One sentence covering the MAIN change, plus brief mention of other significant improvements]
## User Impact
**[Main Feature Category]:**
- [Specific user-facing improvements]
**[Secondary Categories if applicable - e.g., Reliability, Performance]:**
- [Bug fixes with impact]
- [Performance improvements]
## Technical Notes
### 1. [Main Feature Name]
[Detailed explanation of main feature with file references]
### 2. [Bug Fixes / Corrections]
[Each bug fix with location, what was wrong, impact, fix]
### 3. [Infrastructure / Performance]
[Test improvements, framework changes, optimizations]
### 4. [Configuration & Dependencies]
[Constants, config changes, dependency updates]
### 5. [Documentation]
[README updates, new docs, removed obsolete content]
## Testing
[Comprehensive test results with specific numbers]
## Implementation Approach
[List ALL commits with brief explanation of each]
1. **[commit message]** - [what it did]
2. **[commit message]** - [what it did]
...
## Next Steps
[Only if applicable]
---
Generated with [Claude Code](https://claude.com/claude-code)
Before finalizing, verify:
/tmp/pr-summary.md (avoids cluttering repo)gh pr edit --body-file /tmp/pr-summary.md
No PR exists yet:
# Create PR first
gh pr create --title "Title" --body "WIP"
# Then run the update process
Verify base branch:
# Check what base branch the PR is targeting
gh pr view --json baseRefName -q '.baseRefName'
# Or detect default branch if no PR exists
git rev-parse --abbrev-ref origin/HEAD 2>/dev/null | sed 's#origin/##' || echo 'main'
gh CLI not authenticated:
gh auth status
gh auth login
Remember: The PR may contain a week's worth of work across multiple areas. Your job is to tell the complete story, not just the headline feature.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.