About ga-pr
ga-pr is a skill for starting agent work on an existing pull request or branch. It reuses matching tmux sessions and clones, or creates them when needed, and supports merge-conflict tasks.
Key features
- 01Resolve PR numbers, URLs, or branches
- 02Reuse matching tmux sessions
- 03Continue in an existing clone
- 04Clone and check out a PR branch
- 05Handle merge-conflict tasks
Use cases
- 01Apply requested changes to an open PR
- 02Resolve merge conflicts on a PR branch
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ jnsahaj/ skills --skill ga-prAfter installing, type/ga-prin Claude Code to confirm it loaded.
Details
From the project READMEga-pr - Start Follow-up Work on an Existing PR
Kick off an agent task tied to an existing PR or branch. Reuses the existing tmux session/clone for that PR if one already exists.
Steps
-
Get the PR or branch and task from the user's message.
- Accept a PR number, PR URL, or branch name.
- If the task is merge-conflict resolution, use
--merge-conflicts.
-
Run
ga-pr. Default harness is Pi, so omit the harness flag for normal use:ga-pr <pr-number-or-url-or-branch> "<task>"For merge conflicts:
ga-pr --merge-conflicts <pr-number-or-url-or-branch>If the user explicitly asks for Claude Code, pass
--harness c:ga-pr --harness c <pr-number-or-url-or-branch> "<task>" -
Report back with the session, branch, and attach command printed by the script.
Behavior
- Resolves PR inputs through
gh pr view. - Uses the same session naming convention as
ga:<repo>-<branch-slug>. - If a matching tmux session already exists, sends the task into that session instead of creating a duplicate.
- If the clone exists but the session does not, starts a new session in the existing clone.
- If neither exists, clones the repo, checks out the PR branch, and starts the agent.
Rules
- Keep the task concise and direct.
- For conflict resolution, include that the agent should ask before making ambiguous choices.
- Do not use
/create-draft-pr; this command is for updating an existing PR branch.
Comments
Markdown supported