# Github Pr Create

> >

- **Type:** Skill
- **Install:** `agentstack add skill-jie-meng-mythril-agent-skills-github-pr-create`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [jie-meng](https://agentstack.voostack.com/s/jie-meng)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [jie-meng](https://github.com/jie-meng)
- **Source:** https://github.com/jie-meng/mythril-agent-skills/tree/main/mythril_agent_skills/skills/github-pr-create

## Install

```sh
agentstack add skill-jie-meng-mythril-agent-skills-github-pr-create
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# When to Use This Skill

## ZERO-SPECULATION RULE (read this FIRST)

**Once this skill is triggered, do NOT spend ANY tokens analyzing the hostname, guessing the platform, or debating whether `gh` will work.** The correct behavior is:

1. User wants to create a PR → skill is triggered
2. Run `gh` commands → let `gh` succeed or fail
3. If `gh` fails → report the error and suggest `gh auth login --hostname `

**WRONG behavior (NEVER do this):**
- "This appears to be a self-hosted GitLab instance" — WRONG, you don't know that
- "git.company.com looks like GitLab" — WRONG, it could be GitHub Enterprise
- "gh CLI won't work with this host" — WRONG, you haven't tried yet
- Any reasoning about whether the host is GitHub, GitLab, Bitbucket, etc. — WRONG

## Trigger conditions

Trigger this skill when the user wants to **create a Pull Request**:

- "create PR" / "create a PR" / "create pull request"
- "提PR" / "创建PR" / "开PR" / "提交PR" / "发PR"
- "帮我提个PR" / "PR提一下" / "提一下PR"
- "gh pr create" / "submit PR" / "open PR"
- "push and create PR" / "push + PR"
- "create PR to main" / "create PR from this branch"

**NOT a trigger** (do NOT invoke this skill):
- User asks to "review a PR" — use `github-code-review-pr`
- User asks to "view PR" or "list PRs" — use `gh-operations`
- User asks for local git operations — use plain `git`

## Security — MANDATORY rules for AI agents

1. **NEVER echo, print, or log** the values of any environment variable containing credentials (`GH_TOKEN`, `GITHUB_TOKEN`, etc.). Do NOT run commands like `echo $GH_TOKEN` or `printenv GITHUB_TOKEN` — even for debugging.
2. **NEVER pass token/credential values as inline CLI arguments or env-var overrides.** `gh` reads credentials from its own config — just run `gh` commands directly.
3. **When debugging auth errors**, rely solely on `gh auth status` output and `gh` error messages. Do NOT attempt to verify tokens by reading or printing them.
4. **NEVER extract credentials from OS credential stores or config files.** Strictly forbidden commands include:
   - `security find-internet-password`, `security find-generic-password` (macOS Keychain)
   - `git credential fill`, `cat ~/.git-credentials`, `cat ~/.netrc`
   - Reading `~/.config/gh/hosts.yml` or any `gh` auth config file
   - Any command that outputs a password, token, or secret value from any credential store
5. **NEVER use extracted credential values in commands.** Do NOT manually construct authenticated requests (e.g. `curl -H "Authorization: token "`). The `gh` CLI handles all authentication internally — use `gh api` for API calls instead of `curl` with raw tokens.

## Runtime requirements

- **GitHub CLI (`gh`)** installed and authenticated
- **`git`** CLI installed
- Must be inside a git repository with a remote pointing to GitHub (or GitHub Enterprise)
- Run `skills-check github-pr-create` to verify dependencies

# Implementation

## Step 1: Pre-flight Validation

### 1a. Verify current branch is NOT the main/default branch

**This is a hard blocker — do NOT proceed if the user is on the default branch.**

```bash
# Detect default branch
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD --short 2>/dev/null | sed 's|origin/||')
if [ -z "$DEFAULT_BRANCH" ]; then
  DEFAULT_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | awk '{print $NF}')
fi
if [ -z "$DEFAULT_BRANCH" ]; then
  DEFAULT_BRANCH="main"
fi

CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)

if [ "$CURRENT_BRANCH" = "$DEFAULT_BRANCH" ]; then
  echo "ERROR: You are on the default branch ($DEFAULT_BRANCH). Cannot create a PR from the default branch."
  echo "Please switch to a feature branch first."
  exit 1
fi
```

If the user is on the default branch, **stop immediately** and tell them they need to be on a feature/topic branch.

### 1b. Check for unpushed commits

```bash
git status
git log origin/$CURRENT_BRANCH..HEAD --oneline 2>/dev/null
```

If there are unpushed commits, push the branch before creating the PR:

```bash
git push -u origin "$CURRENT_BRANCH"
```

If the remote branch does not exist yet, `git push -u origin HEAD` will create it.

### 1c. Determine the base branch (merge target)

- If the user explicitly specifies a target branch (e.g., "create PR to develop"), use that branch.
- Otherwise, use the detected default branch (`$DEFAULT_BRANCH`).

## Step 2: Gather PR Context

### 2a. Collect commit information

```bash
git log origin/$DEFAULT_BRANCH..HEAD --pretty=format:"%h %s" --no-merges
```

This shows all commits that will be included in the PR.

### 2b. Collect diff summary

```bash
git diff origin/$DEFAULT_BRANCH..HEAD --stat
```

### 2c. Read full diff for PR body generation

```bash
git diff origin/$DEFAULT_BRANCH..HEAD
```

Use this to understand the actual code changes for filling in the PR template.

## Step 3: Detect and Load PR Template

### MANDATORY: Use the bundled template detection script

```bash
python3 scripts/detect_pr_template.py
```

**How to locate the script:**

Check these fixed paths in order. Use the first one that exists:

```python
import pathlib, subprocess, sys

candidates = [
    pathlib.Path.home() / ".config/opencode/skills/github-pr-create/scripts/detect_pr_template.py",
    pathlib.Path.home() / ".claude/skills/github-pr-create/scripts/detect_pr_template.py",
    pathlib.Path.home() / ".copilot/skills/github-pr-create/scripts/detect_pr_template.py",
    pathlib.Path.home() / ".cursor/skills/github-pr-create/scripts/detect_pr_template.py",
    pathlib.Path.home() / ".gemini/skills/github-pr-create/scripts/detect_pr_template.py",
    pathlib.Path.home() / ".codex/skills/github-pr-create/scripts/detect_pr_template.py",
    pathlib.Path.home() / ".qwen/skills/github-pr-create/scripts/detect_pr_template.py",
    pathlib.Path.home() / ".grok/skills/github-pr-create/scripts/detect_pr_template.py",
]
script = next((p for p in candidates if p.exists()), None)
```

The script checks these locations (in order) for PR templates:
1. `.github/pull_request_template.md`
2. `.github/PULL_REQUEST_TEMPLATE.md`
3. `pull_request_template.md`
4. `PULL_REQUEST_TEMPLATE.md`
5. `.github/PULL_REQUEST_TEMPLATE/` directory (multiple templates)
6. `docs/pull_request_template.md`

Machine-readable output:
- `TEMPLATE_FOUND=true|false`
- `TEMPLATE_PATH=` — relative path to the template file
- `TEMPLATE_CONTENT=` — base64-encoded template content
- `MULTIPLE_TEMPLATES=true|false` — whether multiple templates exist
- `TEMPLATE_NAMES=` — names of available templates (when multiple)

### Fallback: Manual template detection

If the script is not found, check template paths manually:

```bash
for f in .github/pull_request_template.md .github/PULL_REQUEST_TEMPLATE.md pull_request_template.md PULL_REQUEST_TEMPLATE.md docs/pull_request_template.md; do
  if [ -f "$f" ]; then
    echo "TEMPLATE_FOUND=true"
    echo "TEMPLATE_PATH=$f"
    break
  fi
done
```

## Step 4: Fill PR Title and Body

### 4a. Generate PR title

The PR title MUST follow the same format as commit messages — see
[`code-review-staged/references/commit-format.md`](../code-review-staged/references/commit-format.md)
for the canonical rules. This keeps PR titles and commit messages
consistent across the codebase.

Quick summary (full rules in `commit-format.md`):

- Format: `[scope]: ` — single line, max 72 characters
- `` from branch prefix: `feat/` → `feat`, `fix/` → `fix`, etc.
- `[scope]` auto-derived from branch name:
  - `//` → scope = JIRA key (e.g. `feat[XYZ-123]: add export endpoint`)
  - `/` with title ≤ 30 chars → scope = lowercase-hyphenated title
  - `/` with title > 30 chars → apply long-title compression (see commit-format.md)
  - `-iter-N` is stripped from scope; `-vN` is kept
  - Bare branches (master/main/dev) → no scope, use `type: subject`
- ``: imperative mood, lowercase first letter, no period, English
- **NEVER use the repo name as scope** — repo identity is already in the PR metadata

When the PR has multiple commits, use the same scope (derived from
the branch name) and write a subject that summarizes the whole PR's
intent.

Examples:

- Branch `feat/XYZ-123/Add-Export` → PR title `feat[XYZ-123]: add CSV and JSON export endpoints`
- Branch `feat/Dark-Mode-Toggle` → PR title `feat[dark-mode-toggle]: add theme switcher in settings`
- Branch `feat/Dark-Mode-Toggle-v2` → PR title `feat[dark-mode-toggle-v2]: add follow-system option`
- Branch `master` → PR title `chore: bump version to 1.2.0` (no scope)

### 4b. Fill PR body

**If a PR template was found (Step 3):**

Fill the template with information from the code changes. Follow these rules strictly:

1. **Sections you CAN fill automatically** — fill them based on the diff and commit messages:
   - Summary / Description / What — describe what the PR does based on actual code changes
   - Changes / What changed — list the key changes
   - Type of change — check the appropriate checkbox based on the nature of changes (bug fix, feature, refactor, etc.)
   - Testing / How to test — describe what was tested if evident from the diff (e.g., new test files added)

2. **Sections you MUST NOT modify unless you have the information:**
   - Screenshots / Screen recordings — leave as-is (AI cannot capture screenshots)
   - Jira ticket / Issue link — only fill if the user provided it, or if the branch name contains a ticket ID (e.g., `feat/XYZ-123/...`)
   - Tech doc / Design doc links — only fill if the user provided them
   - Reviewer checklist — leave as-is for the reviewer
   - Any placeholder with `[link]`, `[url]`, `[screenshot]` — leave the placeholder text as-is

3. **When in doubt, preserve the template's original text.** The user can edit it on the web afterwards. It is better to leave a placeholder than to fill in incorrect information.

**If no PR template was found:**

Generate a reasonable PR body:

```markdown
## Summary

## Changes

- 
- 
- ...
```

### 4c. Language matching

Match the PR body language to the template language if a template is used. If no template, match the user's input language.

## Step 5: Create the PR

### Using `gh pr create`

```bash
gh pr create \
  --base "$BASE_BRANCH" \
  --head "$CURRENT_BRANCH" \
  --title "$PR_TITLE" \
  --body "$PR_BODY"
```

**Additional options based on user request:**
- `--draft` — if user wants a draft PR
- `--reviewer ` — if user specifies reviewers
- `--label ` — if user specifies labels
- `--assignee @me` — if user wants to self-assign

**For GitHub Enterprise (custom host):**

`gh` auto-detects the host from the git remote — no special handling needed. If auth fails, suggest:
```bash
gh auth login --hostname 
```

## Step 6: Output Result

On success, output the PR URL clearly:

```
PR created successfully: https://github.com/owner/repo/pull/123
```

The PR URL is the most important output — make sure the user can see it and click on it.

On failure, report the error and suggest fixes:
- Auth failure → `gh auth login`
- Branch not pushed → `git push -u origin HEAD`
- No commits → explain that there are no changes to create a PR for

# Error Handling

- **Host handling rule (MANDATORY)**: Never pre-stop or branch based on host/domain text. Always run `gh` commands directly.
- **`gh` host/auth error on unknown domain**: Tell the user:
  1. This host might be GitHub Enterprise — run `gh auth login --hostname ` to authenticate
  2. If it's not GitHub at all, this skill only supports GitHub (including GHE)
  - **Do NOT assume the host is "GitLab" or any other platform.**
- **On default branch**: Report clearly that PRs cannot be created from the default branch.
- **No remote**: Suggest `git remote add origin ` or verify the remote is set up.
- **Merge conflicts with base**: Warn the user about potential conflicts but still create the PR. GitHub will show conflict status.
- **Auth failure — ONLY allowed recovery steps**:
  1. Report the `gh` error message to the user
  2. Suggest `gh auth login --hostname `
  3. Suggest `gh auth status --hostname ` to check current auth state
  4. Stop and wait for the user to fix auth

  **FORBIDDEN recovery attempts** (violate Security rules): Do NOT search for credentials in macOS Keychain, git credential stores, `.netrc`, or any other credential storage.

# Examples

### Example 1: Simple PR creation (English)
**User input**: "Create a PR"
**Action**: Check branch → push if needed → detect template → fill body → `gh pr create` → output URL
**Output**: `PR created successfully: https://github.com/owner/repo/pull/42`

### Example 2: PR with target branch (Chinese)
**User input**: "帮我提个PR到develop分支"
**Action**: Check branch → push → use `develop` as base → fill body in Chinese → create PR
**Output**: `PR 创建成功: https://github.com/owner/repo/pull/43`

### Example 3: Draft PR with reviewer
**User input**: "Create a draft PR and add @alice as reviewer"
**Action**: Push → fill body → `gh pr create --draft --reviewer alice`
**Output**: `Draft PR created: https://github.com/owner/repo/pull/44`

### Example 4: PR with Jira context
**User input**: "Create a PR, the Jira ticket is PROJ-456"
**Action**: Push → fill template with Jira link → create PR
**Output**: `PR created successfully: https://github.com/owner/repo/pull/45`

### Example 5: GitHub Enterprise
**User input**: "帮我在 git.mycompany.com 提个PR"
**Action**: Run `gh pr create` directly → if auth error, suggest `gh auth login --hostname git.mycompany.com`
**WRONG behavior**: Saying "this might not be GitHub" — NEVER do this

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [jie-meng](https://github.com/jie-meng)
- **Source:** [jie-meng/mythril-agent-skills](https://github.com/jie-meng/mythril-agent-skills)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** yes
- **Filesystem access:** yes
- **Shell / process execution:** yes
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jie-meng-mythril-agent-skills-github-pr-create
- Seller: https://agentstack.voostack.com/s/jie-meng
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.