# Pr Creator

> A Claude skill from mlhiter/skills.

- **Type:** Skill
- **Install:** `agentstack add skill-mlhiter-skills-pr-creator`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [mlhiter](https://agentstack.voostack.com/s/mlhiter)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [mlhiter](https://github.com/mlhiter)
- **Source:** https://github.com/mlhiter/skills/tree/main/skills/pr-creator

## Install

```sh
agentstack add skill-mlhiter-skills-pr-creator
```

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

## About

# Pull Request Creator

Create high-quality pull requests that follow the repository template and keep
the PR head/base unambiguous.

## Workflow

1. **Branch Management**: Ensure you are not working on `main` or `master`.
   ```bash
   git branch --show-current
   ```
   If needed, create a descriptive branch before making or publishing commits:
   ```bash
   git checkout -b 
   ```

2. **Commit Changes**: Verify all intended changes are committed.
   ```bash
   git status --porcelain
   git diff
   git diff --staged
   ```
   Stage only the files or hunks that belong to the current PR. Do not commit
   unrelated dirty work, secrets, credentials, or direct changes to `main`.

3. **Locate Template**: Search for a pull request template.
   - `.github/pull_request_template.md`
   - `.github/PULL_REQUEST_TEMPLATE.md`
   - `.github/PULL_REQUEST_TEMPLATE/*`

4. **Draft Description**: Fill the template faithfully.
   - Write the PR title and all PR-facing text in English by default, even when
     the conversation with the user is in another language.
   - This includes the title, body, template answers, checklist notes,
     verification notes, and any public PR comments or follow-up text.
   - Do not include Chinese/CJK text in the PR unless the user or repository
     explicitly requires a different public language.
   - Keep the template headings.
   - Mark checklist items only when they are actually complete.
   - Include concise summaries, test results, and related issues when relevant.

5. **Run Preflight**: Run the repository's established verification command
   before creating the PR. If there is no clear preflight command, inspect the
   project docs and use the smallest relevant build, lint, or test command.

6. **Resolve Target, Base, and Head**: Do this before pushing or calling
   `gh pr create`.
   ```bash
   branch="$(git branch --show-current)"
   git branch -vv
   git config --get-regexp "^branch\\.${branch}\\." || true
   git remote -v
   gh repo view --json nameWithOwner,isFork,parent,defaultBranchRef
   ```
   - Resolve the target repository where the PR should be opened.
   - Resolve the base branch from an explicit merge-base config when available
     (`branch..gh-merge-base` or `branch..vscode-merge-base`);
     otherwise compare likely bases and ask if it remains ambiguous.
   - Resolve the intended head owner, head repository, and head remote. In a
     fork-to-upstream workflow, the head is normally the fork owner and the
     target is the upstream owner.
   - Do not treat tracking config (`branch..remote` or
     `branch..merge`) as the PR base.

7. **Push Only to the Intended Head Remote**: Verify both refs, then push the
   current branch to the chosen head remote.
   ```bash
   git ls-remote --heads  
   git push  HEAD:
   git ls-remote --heads  
   ```
   Use `-u` only when binding local tracking to this same intended head is safe
   and explicit.

8. **Create PR with an Owner-Qualified Head**: Write the body to a temporary
   file, scan the title/body for unintended Chinese/CJK text, then create the
   PR with explicit `--repo`, `--head`, and `--base`.
   ```bash
   python3 - "$title" "$body_file"  \
     --head : \
     --base  \
     --title "type(scope): succinct description" \
     --body-file 
   ```

   **Hard stop for fork failures:** If `gh pr create --head :`
   fails because GitHub does not accept that fork head, do not push ``
   to the upstream repository as a same-name fallback, and do not create a PR
   from `upstream:`. Stop and report the failed command, resolved
   target, resolved head, base branch, and error.

   Only after explicit user approval may you use an upstream-owned head as a
   fallback. When approved, prefer a unique upstream branch name, push to that
   exact branch, use an owner-qualified `--head :`, and
   verify the PR head after creation.

9. **Verify PR Head/Base**: After creation, confirm the PR points at the
   intended owner/ref before reporting success.
   ```bash
   gh pr view  \
     --repo  \
     --json url,headRepositoryOwner,headRefName,baseRefName,isCrossRepository,commits
   ```
   The reported `headRepositoryOwner`, `headRefName`, and `baseRefName` must
   match the resolved target. If they do not match, stop and report the mismatch.

## Principles

- Never push to `main` or `master`.
- Never silently switch the PR head owner or remote.
- Always use owner-qualified `--head :` for fork/upstream PRs.
- Never ignore the PR template.
- Keep PR titles, descriptions, checklist text, verification notes, and public
  PR comments in English by default.
- Do not mark checklist items that have not been verified.

## Source & license

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

- **Author:** [mlhiter](https://github.com/mlhiter)
- **Source:** [mlhiter/skills](https://github.com/mlhiter/skills)
- **License:** MIT

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:** no
- **Filesystem access:** yes
- **Shell / process execution:** no
- **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-mlhiter-skills-pr-creator
- Seller: https://agentstack.voostack.com/s/mlhiter
- 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%.