pr

Prompt file imported from gbr5/bloqueio_online (.claude/commands/pr.md). Copyright stays with the author.

Create a pull request for the current branch following PR standards defined in .claude/rules/pr-standards.md.

Steps

1. Check state

   git status
   git log main..HEAD --oneline
   git diff main..HEAD --stat

2. Ensure pushed

   git push -u origin HEAD

3. Analyze changes thoroughly

   • Review all commits and actual code changes since branching from main
   • Identify PR type: feature, fix, refactor, docs, chore
   • Determine the user story: who benefits and why
   • Check for breaking changes or migration needs
   • Note any acceptance criteria that should be verified

4. Create PR using appropriate template

   For Feature PRs (full template):

   gh pr create --title "feat(scope): description" --body "$(cat <<'EOF'
   ## User Story
   
   **As a** [type of user],
   **I want** [goal/desire],
   **So that** [benefit/value].
   
   ## Summary
   
   Brief description of what this PR accomplishes and why.
   
   ## Changes
   
   - Change 1: description
   - Change 2: description
   
   ## Acceptance Criteria
   
   - [ ] Criterion 1: specific, testable condition
   - [ ] Criterion 2: specific, testable condition
   
   ## Testing
   
   - [ ] Unit tests pass
   - [ ] Integration tests pass
   - [ ] Manual testing: [describe what was tested]
   - [ ] No TypeScript errors
   
   ## Screenshots
   
   | Before | After |
   |--------|-------|
   |        |       |
   
   ## Breaking Changes
   
   None
   
   ## Related
   
   - Closes #[issue]
   EOF
   )"

   For Bug Fix PRs:

   gh pr create --title "fix(scope): description" --body "$(cat <<'EOF'
   ## Summary
   
   Brief description of the bug and the fix.
   
   ## Root Cause
   
   Explanation of what caused the bug.
   
   ## Reproduction Steps
   
   1. Step to reproduce
   2. Another step
   
   ## Changes
   
   - Change 1: description
   
   ## Before / After
   
   | Before | After |
   |--------|-------|
   | [bug behavior] | [fixed behavior] |
   
   ## Testing
   
   - [ ] Regression test added
   - [ ] Manual verification completed
   - [ ] All tests pass
   
   ## Related
   
   - Fixes #[issue]
   EOF
   )"

   For Refactor/Docs/Chore PRs (simplified):

   gh pr create --title "refactor(scope): description" --body "$(cat <<'EOF'
   ## Summary
   
   What was refactored/updated and why.
   
   ## Changes
   
   - Change 1
   - Change 2
   
   ## Testing
   
   - [ ] All tests pass
   - [ ] No behavior changes (for refactors)
   EOF
   )"

5. Return the PR URL