create-pr

name	create-pr
description	Create a pull request (GitHub) or merge request (GitLab) from the current branch

Create Pull Request / Merge Request

Create a PR (GitHub) or MR (GitLab) from the current branch with an auto-generated title and description.

Provider detection: Check the remote URL:

• If github.com → use gh CLI
• If gitlab.com or gitlab. → use glab CLI

Arguments

• base-branch (optional): Branch to merge into (defaults to main or repo default)

Prerequisites

You should be working in a repository cloned to /workspace/personal/<repo-name>.

Workflow

1. Verify state — confirm you're in a git repo, not on main/master, and have commits to push.
2. Run PR checks (MANDATORY) — Run ALL checks listed in the "PR Checks" section of your Repository Guidelines. Run each command/task sequentially. If ANY check fails, fix the issue and re-run until all pass. If no guidelines are defined, check the project's CLAUDE.md for a pre-PR checklist and run those. Do NOT proceed until all checks pass.
3. Push the branch — git push -u origin HEAD
4. Gather context — review commit messages and changed files since diverging from base.
5. Generate title and description:
   • Title: Concise summary (conventional commit style if the repo uses it)
   • Description: Summary of changes, notable items, testing done, related issues
6. Create the PR/MR using gh pr create or glab mr create.
7. Check CI status — After creating the PR, wait ~30 seconds, then check CI with gh pr checks <pr-number> (GitHub) or glab mr view --json pipelines (GitLab). If any check is failing, investigate the failure, fix it, push the fix, and re-check. Repeat until CI is green.
8. Report the PR/MR URL and CI status.

Tips

• Link related issues using Fixes #123 or Closes #123 in the description
• Keep PRs focused — one logical change per PR
• If the branch has many commits, summarize the overall change rather than listing each commit