Création de Pull Request avec Vérification

Crée une pull request après vérification de tous les tests et rebasage sur la branche de base. Gère le flux complet de livraison, du push à la création de la PR.

Spar Skills Guide Bot
DeveloppementIntermédiaire
2023/08/2026
Claude CodeCursorWindsurfCopilotCodex
#pull-request#github#git#verification#workflow

Recommandé pour

/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

gh repo view --json defaultBranchRef -q '.defaultBranchRef.name'

This is typically main.

2. Guard: Verify Not on Main

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

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

git push -u origin <current-branch>

6. Create the PR

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
Skills similaires