القائمة
Creates pull requests with quality descriptions. Use when asked to create a PR, open a pull request, or ship code for review. Requires test verification before PR creation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Complete the current milestone and prepare next work by following the canonical complete command doc.
Execute the current plan (from STATE.md -> PLAN.md) by following the canonical execute command doc. Make code changes + run necessary checks.
Initialize project with CLAUDE.md, STATE.md, and ROADMAP.md by following the canonical init command doc.
Create executable plan for the current phase (3-5 tasks). Reads the canonical plan command doc and produces/updates the current PLAN.md referenced from STATE.md. No implementation.
Review code changes and capture learnings for CLAUDE.md by following the canonical review command doc.
Check project progress and suggest the next action by following the canonical status command doc.
| name | creating-pr |
| description | Creates pull requests with quality descriptions. Use when asked to create a PR, open a pull request, or ship code for review. Requires test verification before PR creation. |
Create pull requests with clear descriptions that enable efficient reviews.
NO PR WITHOUT PASSING TESTS
Before creating any PR, verify tests pass. No exceptions.
Run full test suite before anything else:
# Run tests and verify output
npm test # or pytest, go test, etc.
# Check exit code
echo $? # Must be 0
If tests fail: Fix them first. Do not proceed to PR.
# Check current branch
git branch --show-current
# Ensure all changes committed
git status
# Check commits to be included
git log main..HEAD --oneline
# Check diff against target branch
git diff main...HEAD --stat
# Push and set upstream
git push -u origin <branch-name>
Understand the full scope:
# View all commits
git log main..HEAD
# View full diff
git diff main...HEAD
Title format:
<type>: <short description>
Keep under 72 characters. Use imperative mood.
Description structure:
## Summary
Brief explanation of what this PR does and why.
## Changes
- Bullet point of key changes
- Another change
- Third change
## Testing
How to test this PR:
1. Step one
2. Step two
3. Expected result
## Verification
- [x] All tests pass
- [x] Linting passes
- [ ] Manual testing completed
## Notes for Reviewers
- Any specific areas to focus on
- Known limitations
gh pr create --title "type: description" --body "$(cat <<'EOF'
## Summary
What and why.
## Changes
- Change 1
- Change 2
## Testing
1. How to test
2. Expected result
## Verification
- [x] All tests pass
EOF
)"
| Prefix | When to Use |
|---|---|
feat: | New feature |
fix: | Bug fix |
refactor: | Code restructuring |
docs: | Documentation |
test: | Test changes |
chore: | Maintenance |
perf: | Performance |
# Good
feat: add user profile settings page
fix: prevent duplicate form submissions
refactor: extract authentication to middleware
# Bad
Update code
WIP
Fixes
John's changes
Before creating PR:
Do:
Don't:
## Summary
Implement user preferences dashboard.
Closes #123
Fixes #456
Related to #789
Use drafts when:
gh pr create --draft --title "WIP: feature name"
## Summary
Add [feature] to allow users to [benefit].
## Changes
- Add [component/module]
- Update [existing code]
- Add [tests/docs]
## Testing
1. Navigate to [location]
2. Click [action]
3. Verify [expected behavior]
## Verification
- [x] Tests pass
- [x] Linting passes
- [ ] Manual testing done
## Checklist
- [ ] Tests added
- [ ] Documentation updated
- [ ] No console errors
## Summary
Fix [bug] that caused [problem] when [condition].
## Root Cause
[Explanation of why the bug occurred]
## Solution
[How this PR fixes it]
## Testing
1. Previously: [reproduce bug]
2. Now: [verify fix]
3. Regression: [verify no side effects]
## Verification
- [x] Tests pass (including new regression test)
- [x] Bug no longer reproducible
Fixes #[issue-number]
## Summary
Refactor [area] to [improvement].
## Motivation
- [Why this refactoring is needed]
- [What problems it solves]
## Changes
- Extract [X] into [Y]
- Rename [A] to [B]
- Consolidate [duplicated code]
## Verification
- [x] All existing tests pass
- [x] No functional changes
- [x] Performance unchanged
## Notes
This is a pure refactoring with no behavioral changes.