From claude-resources
Creates pull requests from current branch with auto-detected base branch from conversation history, git log, or repo default. Use on 'create pr' phrases or after feature branch work.
npx claudepluginhub takazudo/claude-resources[target-branch]This skill uses the workspace's default tool permissions.
Create a pull request with automatic base branch detection from conversation history, git log, or repository default.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Create a pull request with automatic base branch detection from conversation history, git log, or repository default.
/pr - Create PR with auto-detected base branch/pr <target-branch> - Create PR targeting the specified branchgit status
git branch --show-current
Ensure you're on a feature branch (not main/master/develop).
Priority order for base branch detection:
<target-branch> is provided, use it directlySearch the current conversation for clues about the base branch:
# Fetch latest remote refs
git fetch origin
# Find merge-base with candidate branches
for branch in main master develop staging; do
git merge-base HEAD origin/$branch 2>/dev/null && echo "Found: $branch"
done
# Check which branch has the closest merge-base
# The branch with most recent common ancestor is likely the parent
# Get the default branch
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
gh pr list --head $(git branch --show-current)
If PR exists, ask user if they want to view or update it.
# Get commits
git log origin/<base-branch>..HEAD --oneline
# Get file changes
git diff origin/<base-branch>..HEAD --stat
Before creating, confirm:
<branch-name><base-branch> (with detection method: "specified", "from conversation", "auto-detected", or "default")Optional: Copilot-assisted body draft
Before drafting the body manually, attempt to get a Copilot-drafted body:
DRAFT=$($HOME/.claude/skills/gco/scripts/gco-pr-body.sh "<base-branch>" 2>/dev/null || true)
If $DRAFT is non-empty, use it as the starting point for the body. Claude must still review and adjust it — fill any gaps, fix inaccuracies, and ensure tone/completeness. If the script fails or returns empty, draft the body directly.
# Push if needed
git push -u origin $(git branch --show-current)
# Create PR
gh pr create \
--base <base-branch> \
--title "<title>" \
--body "$(cat <<'EOF'
## Summary
<description>
## Changes
- <change 1>
- <change 2>
## Test Plan
<testing instructions>
EOF
)"
Copilot output is NEVER applied verbatim — always review and adjust before creating the PR.
Display:
The command uses this logic to find the base branch:
gh repo viewIf detection is ambiguous, ask the user to clarify before creating the PR.