Git Pr Create

Create PR

Open GitHub PR for current branch. No confirm.

Flow

1. Base: user names one -> use it. Else detect: git symbolic-ref --short refs/remotes/origin/HEAD -> strip the origin/; ref missing -> git remote set-head origin -a, re-read; no remote -> main, fall back master. Why -> a wrong base makes the PR diff include commits that aren't yours.
2. git fetch origin <base>. Why -> everything below compares against origin/<base>, not the local ref: the local base is often stale or absent entirely (git-branch-create branches off origin/<base> without ever creating it), so a local-ref diff either errors or replays commits already merged.
3. Parallel:
   • git status
   • git branch --show-current
   • git log origin/<base>..HEAD --oneline
   • git diff origin/<base>...HEAD
   • check repo PR template: .github/PULL_REQUEST_TEMPLATE.md, .github/pull_request_template.md, docs/PULL_REQUEST_TEMPLATE.md, root PULL_REQUEST_TEMPLATE.md (first match wins)
4. 0 commits ahead -> stop. Tell user: nothing to PR; commit first via git-commit.
5. Not pushed / behind -> git push -u origin <branch>.
6. Read all branch commits (not just latest). Draft title + body.
   • Template found -> fill that template's structure (preserve headings, checklist items, comment placeholders).
   • No template -> use fallback body below.
7. Derive labels (always pass --label):
   • Map title <type> -> label: feat->enhancement, fix->bug, docs->documentation, test->tests, perf->performance, refactor->refactor, build->build, ci->ci, chore->chore.
   • Breaking change in commits/body -> add breaking-change.
   • Verify labels exist: gh label list --json name -q '.[].name'. Drop any missing; never auto-create.
   • At least 1 label required -> if all dropped, fall back to chore. If chore also missing, surface to user and stop.
8. Heredoc body so markdown survives shell:

   gh pr create --base main --title "feat(auth): add oauth login flow" --label enhancement --body "$(cat <<'EOF'
   # Pull Request Checklist
   
   <!-- Resolves: #123 -->
   
   ## Summary
   
   - swap session cookies for OAuth flow against Google provider
   - persist user via existing `users` table
   
   ## Checklist
   
   - [ ] My code follows the project style guidelines
   - [ ] I have performed a self-review of my code
   EOF
   )"
   

   'EOF' quoted -> no shell interpolation. --base always passed explicitly -> without it gh targets the repo's default branch, silently ignoring a base the user named.
9. Print PR URL.

Title

Same as commits:

<type>(<scope>): <short summary>

• type: build|chore|ci|docs|feat|fix|perf|refactor|test (same set + picks as git-commit)
• scope: optional
• summary: imperative present, lowercase, no .
• Whole title ≤ 72 chars (matches git-commit header limit).

Examples:

• feat(auth): add oauth login flow
• fix(api): handle timeout on retry
• refactor: extract user service

Body — Repo Template Present

• Use the repo template verbatim as the skeleton (headings, order, checklist items, HTML comments).
• Fill Summary with 1–3 bullets, why > what. Obey Length below.
• Tick checklist items that actually apply; leave the rest unchecked.
• If template has a Resolves: / Closes: / Fixes: line and there's a linked issue, fill the number; else drop that line entirely (no #<n> placeholder).
• Preserve untouched any sections you have no content for (e.g. empty Screenshots), unless template explicitly says "remove if N/A".
• Extra prose headings (Context, Testing, Notes, ...) -> ≤ 2 lines each, or leave the placeholder. Never one paragraph per heading.

Fallback Body Template

Use when no repo template exists:

# Pull Request Checklist

<!-- Optional — uncomment if this PR closes an issue -->
<!-- Resolves: #issue-number-here -->

## Summary

<1–3 bullets. Why > what.>

## Checklist

- [ ] My code follows the project style guidelines
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings or errors

• Diff = what. Body = why.
• Linked issue -> uncomment Resolves: line and fill number.
• Breaking -> add ## Breaking changes section + migration notes.

Length

Hard cap: 10 lines of prose for the whole body. Headings, checklists and template boilerplate don't count — only text you write.

• Summary: 1–3 bullets, one line each, ≤ 100 chars. No sub-bullets, no paragraph bullets. Why the char cap -> GitHub soft-wraps, so "one line" alone doesn't bound anything.
• Breaking changes: ≤ 5 lines including migration steps.
• Any other prose section: ≤ 2 lines, or leave its placeholder untouched.
• Nothing to say -> leave the section empty. Silence beats filler.

Prohibitions:

• Why, not what — the diff shows what.
• No restating the title. No file lists, no code dumps, no diff walkthrough.
• No play-by-play ("first X, then Y"). No "this PR does ...".
• No test-plan narration unless the template asks for one.

Good:

## Summary

- swap session cookies for OAuth so sessions survive the API split
- reuse the existing `users` table; no migration needed

Bad — one paragraph per bullet, narrates the diff:

## Summary

- This pull request implements a comprehensive OAuth login flow. It
  replaces the previous session-cookie approach in `auth/session.ts`
  with a new `OAuthProvider` class that handles the token exchange.
- Changes include: adding `oauth.ts`, updating `middleware.ts`,
  refactoring `validateSession`, and updating the auth tests.

Rules

• Always pass --base <base> — the same base resolved in step 1. Never let gh infer it.
• Never PR from main/master against main/master. On base -> stop + ask user to branch (use git-branch-create).
• Never force-push here.
• Never --no-verify unless asked. Why -> pre-push hooks gate CI and secret scans; skipping ships broken code.
• Push or PR-create fail -> surface + fix root cause. No blind retry.
• Always add at least one label (mapped from title <type>, verified to exist via gh label list). Multi-word labels -> quote: --label "needs review". No reviewers / assignees unless asked.
• Open as ready-for-review (no --draft) unless user explicitly asks for a draft PR.
• Body over 10 prose lines -> cut before creating. No "comprehensive" PR descriptions.
• No "Generated with Claude Code" / co-author trailers unless asked.