Generate a GitHub Pull Request message following GitHub's PR template guidelines. Use when the user wants to create a PR, write a pull request description, or asks to summarize changes for a PR.
npx claudepluginhub fuongz/skills --plugin github-write-pr-messageThis skill uses the workspace's default tool permissions.
Generate a well-structured GitHub Pull Request message following GitHub's official PR template guidelines.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
Generate a well-structured GitHub Pull Request message following GitHub's official PR template guidelines.
Additional context (optional): $ARGUMENTS
git branch --show-currentgit log main..HEAD --oneline 2>/dev/null || git log master..HEAD --oneline 2>/dev/null || git log --oneline -10git diff --name-status main..HEAD 2>/dev/null || git diff --name-status master..HEAD 2>/dev/null || git diff --name-status HEAD~1..HEADgit diff main..HEAD 2>/dev/null || git diff master..HEAD 2>/dev/null || git diff HEAD~1..HEADCheck for existing PR templates (in priority order):
.github/pull_request_template.md.github/PULL_REQUEST_TEMPLATE/*.mddocs/pull_request_template.mdpull_request_template.mdIf found, use it as the structure and fill all sections. If not found, use the Default PR Structure below.
fix/123-bug) or commit messages## Summary
<!-- Brief description of what this PR does and why -->
## Changes
-
-
## Related Issues
Closes #<issue-number>
## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Refactoring
- [ ] Documentation update
- [ ] Performance improvement
- [ ] Test addition or update
## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manually tested
## Screenshots / Demo
## Checklist
- [ ] Self-review completed
- [ ] Code follows project style guidelines
- [ ] No new warnings introduced
- [ ] Tests added where applicable
- [ ] Dependent changes merged and published
Present in this order:
feat:, fix:, chore:, etc.)gh pr create@mentions based on changed filesGood:
fix: resolve null pointer in user authenticationfeat: add dark mode support to settings panelBad: Fix bug, Changes, WIP
Closes, Fixes, Resolves) + #issue-number to auto-close issues on merge.github/PULL_REQUEST_TEMPLATE/, present as options and use the most relevantOutput the PR title and body in a code block for easy copy-paste or use with gh pr create.