GI

Streamlines the process of creating GitHub PRs from worktrees and linking them to issues.

Install

mkdir -p .claude/skills/github-pr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12477" && unzip -o skill.zip -d .claude/skills/github-pr && rm skill.zip

Installs to .claude/skills/github-pr

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create a GitHub PR from a worktree branch. Use after committing changes.
72 charsno explicit “when” trigger
Beginner

Key capabilities

  • Verify the current git worktree and branch
  • Check for existing pull requests for the current branch
  • Push the local branch to the remote repository
  • Create a new GitHub pull request with a formatted title and body
  • Update linked GitHub issues with status labels and comments

How it works

The skill verifies the current branch, pushes it to the remote, creates a GitHub pull request with a predefined template, and updates any linked GitHub issues with relevant status labels and comments.

Inputs & outputs

You give it
Current git worktree branch with committed changes
You get back
Created GitHub pull request URL and updated issue status

When to use github-pr

  • Create pull requests
  • Update issue status
  • Manage worktree workflows

About this skill

GitHub PR Workflow (Worktree-Aware)

Prerequisites

Changes committed via git-commit skill.

Workflow

Step 1: Verify Current Location

git worktree list
pwd
BRANCH_NAME=$(git branch --show-current)
echo "Current branch: $BRANCH_NAME"

Step 2: Check for Existing PR

gh pr list --head "$BRANCH_NAME" --state open --repo "$REPO"

If PR exists, show it and exit.

Step 3: Push Branch

git push --set-upstream origin "$BRANCH_NAME"

Step 4: Create PR

gh pr create \
  --repo china-qijizhifeng/NexRL \
  --base main \
  --head "$BRANCH_NAME" \
  --title "type(scope): description" \
  --body "## Summary
- Key change 1
- Key change 2

## Testing
- [ ] Tests pass (`pytest`)
- [ ] Linting clean (`pylint`, `mypy`)
- [ ] Formatting applied (`black`, `isort`)

## Related Issues
Fixes #ISSUE_NUMBER"

Auto-extract title/body from commit messages. No AI branding.

Step 5: Update Issue

ISSUE_NUM=$(echo "$BRANCH_NAME" | grep -oP 'issue-\K\d+')
if [ -n "$ISSUE_NUM" ]; then
  gh issue edit "$ISSUE_NUM" --repo china-qijizhifeng/NexRL \
    --remove-label "status:in-progress" --add-label "status:review" 2>/dev/null || true
  gh issue comment "$ISSUE_NUM" --repo china-qijizhifeng/NexRL \
    --body "✅ PR created: $(gh pr view --json url -q .url). Ready for review."
fi

When not to use it

  • Before committing changes
  • When a PR for the current branch already exists
  • When the issue number cannot be extracted from the branch name

Prerequisites

Changes committed via `git-commit` skill

Limitations

  • Requires committed changes
  • Assumes a specific issue number format in the branch name
  • Uses a predefined PR title and body template

How it compares

This skill automates the entire process of creating a GitHub PR and updating linked issues, including pre-checks and structured formatting, which is more efficient than manual steps.

Compared to similar skills

github-pr side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
github-pr (this skill)05moReviewBeginner
github-workflow-automation112moReviewAdvanced
testing-workflow169moReviewIntermediate
github-actions-templates73moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

Search skills

Search the agent skills registry