Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
create-pr
description
Create a GitHub Pull Request from the current repository's work.
Create PR Skill
Create a Pull Request from current work with automatic branch creation, commit creation, intelligent remote detection, and PR content generation.
Prerequisites Check (MUST verify first)
Before proceeding, verify:
# 1. Check if in a git repository
git rev-parse --is-inside-work-tree
# 2. Check if gh CLI is available and authenticated
gh auth status
# 3. Record the current working tree state
git status --porcelain
If checks fail, STOP and inform the user:
Not in git repo → "This skill requires a git repository. Please navigate to a git project."
gh not authenticated → "Please run gh auth login first."
Do not stop or ask the user to switch branches, commit changes, or stash changes. Handle the current branch and uncommitted changes automatically in the workflow below.
Input
The user may optionally provide:
Target base branch (defaults to main/master)
Draft mode flag
Specific reviewers
Workflow
Step 1: Detect Repository Configuration
# Get all remotes
git remote -v
# Get current branch name
CURRENT_BRANCH=$(git branch --show-current)
# Detect default branch (main or master)
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef -q '.defaultBranchRef.name')
# Get repository info
gh repo view --json owner,name,isFork,parent
Step 2: Identify Upstream and Fork Remotes
Determine the remote configuration:
# List all remotes with their URLs
git remote -v
# Check if this repo is a fork
IS_FORK=$(gh repo view --json isFork -q '.isFork')
# If it's a fork, get parent infoif [ "$IS_FORK" = "true" ]; then
PARENT_OWNER=$(gh repo view --json parent -q '.parent.owner.login')
PARENT_NAME=$(gh repo view --json parent -q '.parent.name')
fi
Remote Classification Logic:
Scenario
Upstream Remote
Push Remote
Single remote (origin)
origin
origin
Fork: origin=fork, upstream=parent
upstream
origin
Fork: origin=parent, fork remote exists
origin
fork remote
Multiple remotes, one is fork
non-fork remote
fork remote
Detection Algorithm:
# Get current user's GitHub username
CURRENT_USER=$(gh api user -q '.login')
# For each remote, check if it belongs to current userfor remote in $(git remote); do
REMOTE_URL=$(git remote get-url $remote)
# Extract owner from URL (handles both HTTPS and SSH)
REMOTE_OWNER=$(echo"$REMOTE_URL" | sed -E 's/.*[:/]([^/]+)\/[^/]+\.git$/\1/' | sed 's/\.git$//')
if [ "$REMOTE_OWNER" = "$CURRENT_USER" ]; then
FORK_REMOTE=$remoteelse
UPSTREAM_REMOTE=$remotefidone# Default fallback
UPSTREAM_REMOTE=${UPSTREAM_REMOTE:-origin}
FORK_REMOTE=${FORK_REMOTE:-origin}
Step 3: Create a Feature Branch and Commit Changes
Prepare the work for a PR before rebasing or pushing:
Inspect git status --short, staged changes, unstaged changes, and untracked file names.
If CURRENT_BRANCH is DEFAULT_BRANCH, main, or master, generate a concise branch name from the user's request and the changes. Follow repository naming conventions when present, avoid collisions with local and remote branches, create the branch, and update CURRENT_BRANCH.
If the working tree contains changes, stage the intended current work and commit it. Generate a concise commit message from the request and diff, and follow repository commit style, sign-off, and signing requirements.
Perform the branch creation and commit without asking the user to choose a branch name, switch branches, provide a commit message, or commit the changes themselves.
# Create a feature branch automatically when currently on the base branch.if [ "$CURRENT_BRANCH" = "$DEFAULT_BRANCH" ] || \
[ "$CURRENT_BRANCH" = "main" ] || \
[ "$CURRENT_BRANCH" = "master" ]; then# Derive NEW_BRANCH from the request and diff, for example feat/add-export.# Add a short numeric suffix if the name already exists locally or remotely.
git switch -c "$NEW_BRANCH"
CURRENT_BRANCH=$NEW_BRANCHfi# Commit all intended current work when the tree is dirty.if [ -n "$(git status --porcelain)" ]; then
git status --short
git diff
git diff --cached
git add -A
git diff --cached
# Derive COMMIT_MESSAGE from the request and staged diff. Add flags such as# -s or -S when required by repository instructions.
git commit -m "$COMMIT_MESSAGE"fi
Do not include editor artifacts, generated secrets, credentials, or unrelated files in the commit. If repository instructions require tests before committing, run them and include the result in the PR description.
Step 4: Sync and Rebase onto the Upstream Default Branch
# Fetch latest from upstream
git fetch "$UPSTREAM_REMOTE""$DEFAULT_BRANCH"# Rebase current branch onto latest default branch
git rebase "$UPSTREAM_REMOTE/$DEFAULT_BRANCH"# If rebase fails, inform userif [ $? -ne 0 ]; thenecho"Rebase failed. Please resolve conflicts manually."
git rebase --abort
exit 1
fi
Step 5: Push Branch to Remote
Check if branch exists on remote and push:
# Check if branch exists on the push remote
REMOTE_BRANCH_EXISTS=$(git ls-remote --heads $FORK_REMOTE$CURRENT_BRANCH | wc -l)
if [ "$REMOTE_BRANCH_EXISTS" -eq 0 ]; then# Branch doesn't exist, push with upstream tracking
git push -u $FORK_REMOTE$CURRENT_BRANCHelse# Branch exists, force push (after rebase) with lease for safety
git push --force-with-lease $FORK_REMOTE$CURRENT_BRANCHfi
Important: Always use --force-with-lease instead of --force for safety.
Step 6: Gather PR Content Information
# Get all commits between default branch and current branch
git log$UPSTREAM_REMOTE/$DEFAULT_BRANCH..HEAD --pretty=format:"%h %s%n%b" --no-merges
# Get the diff summary
git diff --stat$UPSTREAM_REMOTE/$DEFAULT_BRANCH..HEAD
# Get the full diff for analysis
git diff $UPSTREAM_REMOTE/$DEFAULT_BRANCH..HEAD
# Get list of changed files
git diff --name-only $UPSTREAM_REMOTE/$DEFAULT_BRANCH..HEAD
Step 7: Check for PR Template
# Check for PR template in common locations
PR_TEMPLATE=""for template_path in \
".github/pull_request_template.md" \
".github/PULL_REQUEST_TEMPLATE.md" \
"docs/pull_request_template.md" \
"PULL_REQUEST_TEMPLATE.md"; doif [ -f "$template_path" ]; then
PR_TEMPLATE="$template_path"breakfidone# Also check for template directoryif [ -z "$PR_TEMPLATE" ] && [ -d ".github/PULL_REQUEST_TEMPLATE" ]; then# Use default template if existsif [ -f ".github/PULL_REQUEST_TEMPLATE/default.md" ]; then
PR_TEMPLATE=".github/PULL_REQUEST_TEMPLATE/default.md"fifi# Read template content if foundif [ -n "$PR_TEMPLATE" ]; thencat"$PR_TEMPLATE"fi
Step 8: Generate PR Title and Description
Title Generation Rules:
If single commit: Use commit message subject line
If multiple commits: Summarize the overall change
Follow conventional commit format if project uses it: <type>(<scope>): <description>
Keep under 72 characters
Description Generation:
If PR template exists, fill in the template sections:
Common Template Section
How to Fill
## Summary / ## Description
Summarize changes from commits and diff
## Changes / ## What
List key changes from diff
## Why / ## Motivation
Extract from commit bodies or infer from changes
## Testing
List test files changed or suggest manual testing
## Screenshots
Leave placeholder if UI changes detected
## Checklist
Leave checkboxes for user to complete
Fixes # / Closes #
Extract issue references from commits
If no template, generate structured description:
## Summary
[2-3 sentences summarizing what this PR does]
## Changes- [Key change 1]
- [Key change 2]
- [Key change 3]
## Testing
[How the changes were tested or should be tested]
---
[Any issue references found in commits]
Step 9: Create the Pull Request
# Determine the base repository for the PRif [ "$IS_FORK" = "true" ]; then# For forks, create PR against parent repo
BASE_REPO="$PARENT_OWNER/$PARENT_NAME"
gh pr create \
--repo "$BASE_REPO" \
--base "$DEFAULT_BRANCH" \
--head"$CURRENT_USER:$CURRENT_BRANCH" \
--title "$PR_TITLE" \
--body "$PR_BODY"else# For non-forks, create PR in same repo
gh pr create \
--base "$DEFAULT_BRANCH" \
--head"$CURRENT_BRANCH" \
--title "$PR_TITLE" \
--body "$PR_BODY"fi
