github-workflow

name	github_workflow
description	Guides Claude through the full GitHub PR lifecycle — branch naming, push, review responses, and merge. Loaded automatically before any push, PR creation, review response, or merge action.
user-invocable	false
effort	high
allowed-tools	Bash(git *) Bash(gh *) Bash(.claude/scripts/*) Read

Load this skill before any push, PR creation, review response, or merge action.

Quick reference

Step	Pattern
Branch	<type>/<PROJECT-KEY>-<n>-<kebab-slug> e.g. feat/PI-42-add-oauth
PR title	[PROJECT-123][type] description e.g. [PI-42][feat] Add OAuth login
No-issue PR	[nojira][type] description e.g. [nojira][fix] Fix typo
PR body	Must include Closes #N (skip for nojira)

Types: feat fix chore docs test

Standard lifecycle

1. Start work — use the start_task skill. It runs start_issue.sh which creates the branch, pushes, and opens a draft PR. For minor no-issue work, use .claude/scripts/create_nojira_pr.sh <type> "description".

2. Push during development:

   .claude/scripts/push_branch.sh
   

   Never use bare git push — push_branch.sh retries transient GitHub errors.

3. Finish — push, mark ready, and merge:

   .claude/scripts/finish_pr.sh [pr-number]
   

   finish_pr.sh pushes, marks the draft ready, runs monitor_pr.sh --merge, and handles review cycles automatically.

   Or run steps individually:

   .claude/scripts/push_branch.sh
   .claude/scripts/promote_review.sh [pr-number]
   .claude/scripts/monitor_pr.sh <pr-number> --merge
   

Review cycle protocol

monitor_pr.sh --merge exits 1 for CI or merge failures and 2 when review/decision fails while review cycles remain. Treat any non-zero exit as unfinished work: inspect the printed failure, fix or retry, then rerun the workflow. Do not report a PR as merged unless the script exits 0 after printing the merged or auto-merge-enabled status.

1. Post a response for each review comment:

   gh pr comment <pr-number> --body "**Review response:**
   - [comment]: Fixing — <reason>
   - [comment]: Not applying — <reason>"
   

2. Fix actionable code, then push: .claude/scripts/push_branch.sh
3. Re-run with the next cycle number:

   .claude/scripts/monitor_pr.sh <pr-number> --merge --review-cycle <N>
   

4. After 1 review-fix cycle, the script auto force-merges with --admin.

Before applying any comment: read the current file state. Check whether the comment is stale (already fixed), contradicts conventions, or is correct. Never blindly apply a suggestion — post reasoning even when rejecting.

Issue titles vs PR titles

• Issue titles: plain description only — type is carried by the label.
• PR titles: must include [type] — PR titles become merge commit messages in git log.
• nojira: for minor fixes without a tracking issue; no Closes #N needed.