From pr-conventions
Pull request conventions for comprehensive commit analysis and test planning. Use when creating or reviewing pull requests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pr-conventions:pr-conventionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When creating a pull request, **always analyse the full commit history** — not just the latest commit.
When creating a pull request, always analyse the full commit history — not just the latest commit.
git diff [base-branch]...HEAD to see all changes since the branch divergedgit log [base-branch]..HEAD to review every commit messageEvery PR must include a Test plan section with a bulleted TODO checklist:
## Test plan
- [ ] Unit tests pass for new functionality
- [ ] Integration tests cover the critical path
- [ ] Manual verification of [specific behaviour]
- [ ] Edge cases tested: [list them]
When pushing a new branch for the first time, always use the -u flag:
git push -u origin <branch-name>
npx claudepluginhub shawn-guo-cn/agentfoundry-plugin-marketplace --plugin pr-conventionsPrepares PRs by validating tests, analyzing git history, and generating structured PR bodies. Useful when contributing to external repositories.
Creates pull requests with clear descriptions and test plans. Analyzes branch changes, detects ticket references, and runs code review before PR creation.