Invoking this skill IS the request. Your task is fully specified here. Never ask what to do.
Your first Bash call is cd "$(git rev-parse --show-toplevel)", alone, once. The working directory persists across Bash calls, so run every later command bare, exactly as written below. A cd ... && or $() prefix stops a command matching allowed-tools, and the merge then hits the permission gate.
The user invoked this skill with: "$ARGUMENTS"
Mode comes from the arguments first: create means create mode, update means update mode, merge means merge mode. With none of those three words, including an empty argument, run gh pr view --json state --jq .state 2>/dev/null and let its result decide: a non-zero exit (no PR for this branch) means create mode, OPEN means update mode, any other state means report that state and stop. Merge mode only ever comes from the argument.
PR material
Create mode and update mode run these steps where they say "gather PR material":
git log --format='%n%s' --name-only main..HEAD (fall back to master..HEAD). Each commit is a block: its subject, then the files it touched. A flat log next to a branch-wide diff stat lets the writer guess which commit touched which file.- The PR describes the net change of the branch. A commit whose subject starts with
Revert " and the commit it names cancel each other when both sit in the log, and a subject starting with chore: bump describes no change. Remove those blocks from the log before passing it on.
- Invoke the
hal-skills:write-like-me skill. Pass as argument: "Write a GitHub PR title and body. Output the title as the first line, a blank line, then the body, with no labels or headings around them. Title: one plain-English line, no type prefix, under 72 chars, no backticks. Body: 1-3 sentences of prose — what changed, why. No headings, no lists. In the body, wrap every file path, command, flag, and identifier in backticks, at every occurrence, like plugins/hal-output-styles/plugin.json, ~/.claude/skills, hal sync, say-no-more. Material:" followed by the log from step 2.
- From
write-like-me's output, take the first line as title, the rest as body.
Create mode
git rev-parse --abbrev-ref HEAD — abort if main or master.gh pr view --json url 2>/dev/null — if a PR already exists, report its URL and stop.git push -u origin HEAD.- Gather PR material.
gh pr create --title "<title>" --body "<body>".- Report the PR URL.
Update mode
gh pr view --json url,state 2>/dev/null — abort if no PR or not open.git log --oneline @{u}..HEAD — if it lists commits, git push so the PR shows them.- Gather PR material.
gh pr edit --body "<body>" — the title stays as it is.- Report the PR URL.
Merge mode
gh pr view --json url,number,state — abort if no PR or not open.git log --oneline @{u}..HEAD — if it lists commits, git push so CI and the merge see them.gh pr checks --watch — blocks until all checks complete. Use a 10-minute Bash timeout. If you pushed and it reports no checks yet, the push just queued them: wait 15 seconds and run it again once.- If exit code 0 (all checks passed):
gh pr merge --merge --delete-branchgit switch main && git pull- Delete local branch if it still exists:
git branch -d <branch>
- Report: merged, remote and local branches cleaned up.
- If non-zero (check failed):
- Run
gh pr checks once more to list failed checks and their URLs.
- Report which checks failed. Take no other action.
1---2name: pr3description: Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits, or wait for CI and merge it4---56Invoking this skill IS the request. Your task is fully specified here. Never ask what to do.78Your first Bash call is `cd "$(git rev-parse --show-toplevel)"`, alone, once. The working directory persists across Bash calls, so run every later command bare, exactly as written below. A `cd ... &&` or `$()` prefix stops a command matching `allowed-tools`, and the merge then hits the permission gate.910The user invoked this skill with: "$ARGUMENTS"1112Mode comes from the arguments first: `create` means create mode, `update` means update mode, `merge` means merge mode. With none of those three words, including an empty argument, run `gh pr view --json state --jq .state 2>/dev/null` and let its result decide: a non-zero exit (no PR for this branch) means create mode, `OPEN` means update mode, any other state means report that state and stop. Merge mode only ever comes from the argument.1314## PR material1516Create mode and update mode run these steps where they say "gather PR material":17181. `git log --format='%n%s' --name-only main..HEAD` (fall back to `master..HEAD`). Each commit is a block: its subject, then the files it touched. A flat log next to a branch-wide diff stat lets the writer guess which commit touched which file.192. The PR describes the net change of the branch. A commit whose subject starts with `Revert "` and the commit it names cancel each other when both sit in the log, and a subject starting with `chore: bump` describes no change. Remove those blocks from the log before passing it on.203. Invoke the `hal-skills:write-like-me` skill. Pass as argument: "Write a GitHub PR title and body. Output the title as the first line, a blank line, then the body, with no labels or headings around them. Title: one plain-English line, no type prefix, under 72 chars, no backticks. Body: 1-3 sentences of prose — what changed, why. No headings, no lists. In the body, wrap every file path, command, flag, and identifier in backticks, at every occurrence, like `plugins/hal-output-styles/plugin.json`, `~/.claude/skills`, `hal sync`, `say-no-more`. Material:" followed by the log from step 2.214. From `write-like-me`'s output, take the first line as title, the rest as body.2223## Create mode24251. `git rev-parse --abbrev-ref HEAD` — abort if `main` or `master`.262. `gh pr view --json url 2>/dev/null` — if a PR already exists, report its URL and stop.273. `git push -u origin HEAD`.284. Gather PR material.295. `gh pr create --title "<title>" --body "<body>"`.306. Report the PR URL.3132## Update mode33341. `gh pr view --json url,state 2>/dev/null` — abort if no PR or not open.352. `git log --oneline @{u}..HEAD` — if it lists commits, `git push` so the PR shows them.363. Gather PR material.374. `gh pr edit --body "<body>"` — the title stays as it is.385. Report the PR URL.3940## Merge mode41421. `gh pr view --json url,number,state` — abort if no PR or not open.432. `git log --oneline @{u}..HEAD` — if it lists commits, `git push` so CI and the merge see them.443. `gh pr checks --watch` — blocks until all checks complete. Use a 10-minute Bash timeout. If you pushed and it reports no checks yet, the push just queued them: wait 15 seconds and run it again once.454. If exit code 0 (all checks passed):46 - `gh pr merge --merge --delete-branch`47 - `git switch main && git pull`48 - Delete local branch if it still exists: `git branch -d <branch>`49 - Report: merged, remote and local branches cleaned up.505. If non-zero (check failed):51 - Run `gh pr checks` once more to list failed checks and their URLs.52 - Report which checks failed. Take no other action.
vinta