create-pr

Create PR

Plugin Resource Resolution

<PLUGIN_ROOT> is notation. Replace it with a concrete absolute plugin root before every resource read or command:

• Codex: Start from the directory containing the absolute selected SKILL.md path, then ascend two directories (skills/<name> -> plugin root).
• Claude Code: Bind it to the injected ${CLAUDE_PLUGIN_ROOT} value.

Create a pull request following the repo's PR template and conventions.

Before requesting decisions, read <PLUGIN_ROOT>/lib/driver-interaction.md and follow its cross-platform capability-binding rules.

Read <PLUGIN_ROOT>/lib/decision-gates.md before resolving template selection.

Usage

$go-workflow:create-pr

Steps

Step 1: Gather Context

CURRENT_BRANCH=$(git branch --show-current)
DEFAULT_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | sed 's/.*: //')
git log "${DEFAULT_BRANCH}..HEAD" --oneline
git diff "${DEFAULT_BRANCH}..HEAD" --stat

Step 2: Branch Protection

If the current branch is main, master, or matches the default branch:

WORKFLOW_RESULT=INCOMPLETE
WORKFLOW_REASON=default-branch

Stop without pushing or creating a PR.

Step 3: Push Branch

Ensure the branch is pushed to the remote:

git push -u origin "$CURRENT_BRANCH"

Step 4: Find PR Template

Check for a PR template in these locations (in order):

cat .github/pull_request_template.md 2>/dev/null || \
cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || \
cat docs/pull_request_template.md 2>/dev/null || \
cat pull_request_template.md 2>/dev/null || \
echo "NO_TEMPLATE"

If a template directory exists, resolve a driver-resolvable gate. Prefer an explicit repository configuration or the template whose name and required sections match the change type. Otherwise choose the general-purpose template, or the first lexical template when all candidates are equally general. State Decision, Evidence, and Rationale; do not request input.