Creates a PR after verifying all checks pass. Handles the full ship workflow: verify, push, create PR.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add luthersystems/elps --skill pr --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pr?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/luthersystems-elps)More formats (shields.io, HTML) on the badges page.
# /pr — Pull Request Creation Skill
Creates a PR after verifying all checks pass. Handles the full ship workflow: verify, push, create PR.
## Trigger
Use when asked to create a PR, submit changes for review, or ship changes.
## Workflow
### 1. Determine Base Branch
```bash
gh repo view --json defaultBranchRef -q '.defaultBranchRef.name'
```
This is typically `main`.
### 2. Guard: Verify Not on Main
```bash
current=$(git branch --show-current)
if [ "$current" = "main" ] || [ "$current" = "master" ]; then
echo "ERROR: On $current — create a feature branch first"
exit 1
fi
```
**STOP** if on main/master. Create a feature branch before proceeding. Never push directly to the default branch.
### 3. Fetch and Rebase
```bash
git fetch origin
git rebase origin/<base-branch>
```
If there are conflicts, resolve them before proceeding.
### 4. Run Full Verification
Run the complete `/verify` pipeline (all 6 steps). If any step fails, stop and fix before creating the PR.
### 5. Push
```bash
git push -u origin <current-branch>
```
### 6. Create the PR
```bash
gh pr create --title "<concise title>" --body "$(cat <<'EOF'
## Summary
- <bullet point describing what changed>
- <bullet point describing why>
## Test Plan
- [ ] `make test` passes
- [ ] `make static-checks` passes
- [ ] `./elps fmt -l ./...` reports no changes
- [ ] `./elps lint ./...` reports no diagnostics
- [ ] `./elps doc -m` reports no missing docs
Closes #<N>
EOF
)"
```
### 7. Report
Return the PR URL so the user can review it.
## PR Title Guidelines
- Keep under 70 characters
- Use imperative mood: "Add ...", "Fix ...", "Update ..."
- Be specific: "Add rethrow builtin for handler-bind" not "Add new feature"
## PR Body Guidelines
- **Summary**: 1-3 bullet points explaining what and why
- **Test Plan**: Checklist of verification steps
- **Closes #N**: Link to the issue if this PR resolves one
- Include the Claude Code attribution line
## Checklist
- [ ] All changes committed
- [ ] Rebased on latest base branch
- [ ] Full verify pipeline passes
- [ ] Pushed to remote with `-u` flag
- [ ] PR created with summary, test plan, and issue link
- [ ] PR URL returned to user
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!