| name | pr-creator |
| description | Create, draft, format, validate, or open pull requests for the wizteros repository according to its CLAUDE.md rules. Use when asked to "create a PR", "open a pull request", "draft the PR", "write a PR title/body", or check PR formatting for a branch in wizteros. |
Create wizteros pull requests
Follow the repository's current rules and create a pull request only when the user has
explicitly asked for one.
Respect authorization boundaries
- Read the repository-root
CLAUDE.md before preparing a pull request. Treat it as the
source of truth when it differs from this skill.
- Treat requests to create or open a pull request as authorization for that action only.
Do not create or switch branches, commit, push, or merge unless the user separately
authorizes those actions.
- For requests to draft, write, format, review, or validate PR text, return the proposed
title and body without opening a pull request.
Inspect the branch
- Confirm the current repository root and current branch.
- Determine the remote's default branch and use it as the base unless the user names a
different base.
- Inspect the complete committed branch diff and commit history against the base. Do not
derive the PR from only the latest commit or the working-tree diff.
- Check for uncommitted changes and report that they will not be included in the PR.
- Check whether the current branch already has a pull request. Do not create a duplicate;
return the existing PR instead.
- Confirm every intended commit exists on the remote branch. If a push is required, stop
with the prepared title and body and ask for explicit push authorization.
Typical inspection commands are:
git rev-parse --show-toplevel
git status --short --branch
gh repo view --json defaultBranchRef -q .defaultBranchRef.name
git log --oneline <base>..HEAD
git diff --stat <base>...HEAD
git diff <base>...HEAD
git branch -vv
gh pr list --head <head> --state all --json url,title,state
Use equivalent GitHub tooling when gh is unavailable.
Format the pull request
- Start the title with exactly
WZ: , followed by a short, specific description of the
branch's logical change.
- Keep the body minimal and use concise
- bullet points.
- Describe only changes present in the committed branch diff.
- Mention verification only when it actually ran; never imply that unrun checks passed.
- Omit boilerplate, repeated title text, empty headings, and speculative follow-up work.
Example:
WZ: Add subscription renewal handling
- process successful renewal webhooks
- add regression coverage for renewal state changes
Before creation, validate that the title matches WZ: <short title> and that the body
remains a minimal bullet list under the current CLAUDE.md rules.
Create and verify
Prefer the connected GitHub integration when available. Otherwise, create the pull request
with explicit values rather than --fill:
gh pr create --base <base> --head <head> --title '<title>' --body '<body>'
Add --draft only when the user requests a draft. After creation, read the pull request
back from GitHub, verify its title, body, base, head, and draft state, then return its URL.
