🇺🇸English
PR Preparation Skill
Systematic PR preparation that validates tests and generates high-quality PR bodies.
Overview
Prepares contributions by analyzing the target repo's conventions, git history, test coverage, and generating properly-formatted PR bodies.
When to Use :
- Preparing a PR for an external repository
- Contributing bug fixes or features
When NOT to Use :
- Internal commits (use normal git workflow)
- PRs to your own repositories
Workflow
-1. Prior Work Check -> BLOCKING: Final check for competing PRs
0. Isolation Check -> BLOCK if PR mixes unrelated changes
1. Context Discovery -> Understand target repo conventions
2. Git Archaeology -> Analyze commit patterns, PR history
3. Pre-Flight Checks -> Run tests, linting, build
4. Change Analysis -> Summarize what changed and why
5. PR Body Generation -> Create structured PR description
6. USER REVIEW GATE -> STOP. User must approve before submission.
7. Submission -> Only after explicit user approval
Phase 0: Isolation Check (BLOCKING)
CRITICAL : Run this FIRST. Do not proceed if PR mixes unrelated changes.
Commit Type Analysis
# Extract commit type prefixes from branch
git log --oneline main..HEAD | sed 's/^[^ ]* //' | grep -oE '^[a-z]+(\([^)]+\))?:' | sort -u
Rule : If more than one commit type prefix exists, the PR is mixing concerns.
File Theme Analysis
# List all files changed vs main
git diff --name-only main..HEAD
# Group by directory
git diff --name-only main..HEAD | cut -d'/' -f1-2 | sort -u
Isolation Checklist
| Check | Pass Criteria |
|---|
| Single commit type | All commits share same prefix |
| Thematic files | All changed files relate to PR scope |
| No main overlap | Changes not already merged |
| Atomic scope | Can explain in one sentence |
DO NOT PROCEED IF ISOLATION CHECK FAILS.
CRITICAL: User Review Gate
NEVER submit a PR without explicit user approval.
After generating the PR body (Phase 5), ALWAYS:
- Write the PR body to a file for review
- Show the user what will be submitted
- STOP and ask : "Ready to submit? Review the PR body above."
- Wait for explicit approval before running
gh pr create
# Write PR body to file
cat > /tmp/pr-body.md << 'EOF'
<generated PR body>
EOF
# Show user
cat /tmp/pr-body.md
# ASK - do not proceed without answer
echo "Review complete. Submit this PR? [y/N]"
Phase 3: Pre-Flight Checks
# Go projects
go build ./...
go vet ./...
go test ./... -v -count=1
# Node projects
npm run build
npm test
# Python projects
pytest -v
Pre-Flight Checklist
- Code compiles without errors
- All tests pass
- No new linting warnings
- No secrets or credentials in code
Phase 5: PR Body Generation
Standard Format
## Summary
Brief description of WHAT changed and WHY. 1-3 sentences.
Start with action verb (Add, Fix, Update, Refactor).
## Changes
Technical details of what was modified.
## Test plan
- [x] `go build ./...` passes
- [x] `go test ./...` passes
- [x] Manual: <specific scenario tested>
Fixes #NNN
Key conventions:
- Test plan items are checked
[x] (you ran them before PR)
Fixes #NNN goes at the end
Phase 7: Submission (After Approval Only)
# Create PR with reviewed body
gh pr create --title "type(scope): brief description" \
--body "$(cat /tmp/pr-body.md)" \
--base main
Remember : This command should ONLY run after user explicitly approves.
Anti-Patterns
| DON'T | DO INSTEAD |
|---|
| Submit without approval | ALWAYS stop for user review |
| Skip isolation check | Run Phase 0 FIRST |
| Bundle lint fixes into feature PRs | Lint fixes get their own PR |
| Giant PRs | Split into logical chunks |
| Vague PR body | Detailed summary with context |
| Skip pre-flight | Always run tests locally |
Examples
Prepare External PR Body
User says: "Prepare this branch for PR submission."
What happens:
- Run isolation and pre-flight validation.
- Build structured PR body with summary and test plan.
- Pause for mandatory user review before submit.
Evidence-First PR Packaging
User says: "Generate a high-quality PR description with clear verification steps."
What happens:
- Gather git archaeology and test evidence.
- Synthesize concise rationale and change list.
- Produce submit-ready body pending approval.
Troubleshooting
| Problem | Cause | Solution |
|---|
| PR body is weak | Missing context from commits/tests | Re-run evidence collection and expand summary |
| Submission blocked | Mandatory review gate not passed | Get explicit user approval before gh pr create |
| Test plan incomplete | Commands/results not captured | Add executed checks and outcomes explicitly |
| Title/body mismatch | Scope drift during edits | Regenerate from latest branch diff and constraints |
Reference Documents
Weekly Installs
130
Repository
boshu2/agentops
GitHub Stars
198
First Seen
Feb 18, 2026
Security Audits
Gen Agent Trust HubPassSocketFailSnykWarn
Installed on
opencode130
github-copilot126
codex126
kimi-cli126
gemini-cli126
amp126
