Menü
Generates pull request titles and descriptions from git diffs. Use for any PR creation or update.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Pulls review findings and CI status on the current branch's open PR, fixes each in the working tree, refreshes any stale `.claude/` docs, replies with a summary comment, and pushes a follow-up commit. The worker's return leg after `claude-pr-review`. Use when asked to "address the review", "fix the PR comments", "respond to review", or after an orchestrator posts findings. Do NOT use to write a review. That is `claude-pr-review`.
Ships a small self-review edit on the current PR branch by staging, committing, pushing, and syncing the open PR, replying on the PR when it carries review comments. Use when asked to "ship a followup", "push the PR fix", "followup", or "commit and push this small change". Do NOT use when there is no open PR for the branch (use git-ship instead).
Claude skill structure and authoring rules
Chains implement → verify → review → ship after a feature plan is approved. Reads the plan for the current branch, runs the full pipeline in one session, and stops on any failure or non-minor review finding. Use when asked to "autoship", "ship this feature end to end", or "run the chain". Do NOT auto-trigger. Requires an approved plan file.
Asserts the orchestrator role for the current session and holds the build loop, dispatching to the roadmap, feature, review, and worktree skills. Use when asked to "be the orchestrator", "run the orchestrator", "orchestrate this project", or to set up the control session for parallel feature builds. Do NOT build features or merge PRs in this session.
Reviews an open pull request from an independent session and posts findings as a review comment on the PR. Reads project docs and the roadmap for cross-feature context a self-review lacks. Use when asked to "review the PR", "review this feature's PR", "post a PR review", or acting as the orchestrator reviewing a worker's PR. Do NOT use to review local uncommitted changes. That is `claude-review`.
| name | git-pr |
| description | Generates pull request titles and descriptions from git diffs. Use for any PR creation or update. |
Read these files from the project root in parallel:
.claude/standards/branch.md: branch format, valid types, and constraints.claude/standards/pr.md: structure, rules, and banned phrases.claude/standards/prose.md: prose conventions for all generated text.claude/standards/versioning.md: phase label vs semver disciplineThen run these commands in parallel to gather git context:
git remote get-url origin 2>/dev/null || echo "NO_REMOTE"git branch --show-current 2>/dev/null || echo "unknown"git log main..HEAD --oneline 2>/dev/null || echo "NO_COMMITS"git diff main..HEAD -- . ':(exclude)*.lock' ':(exclude)*-lock.json' 2>/dev/null || echo "NO_DIFF"<type>/<description> format (valid types are defined in .claude/standards/branch.md), stop and output:
❌ Branch name does not follow conventions. Run /git-branch to rename first.❌ No commits ahead of main. Nothing to PR.After outputting the preview, execute the final command immediately. Claude Code's tool permission dialog is the confirmation gate. Do not wait for user input.
In the generated ## Testing section, mark items Claude executed this session as - [x]. Leave items that need human verification (visual UX, reviewer sanity checks) as - [ ]. Never pre-check based on intent or past sessions.
Before running the final command, scan the PR title and body for banned characters and rewrite each occurrence:
— (em dash): split into two sentences or use a comma; (semicolon): split into two sentencesThese bans come from .claude/standards/prose.md and apply to PR text on top of .claude/standards/pr.md. Reading prose.md is not enough. The scan is an explicit step.
Detect an existing PR and branch: edit it in place when one is open, create it otherwise. This keeps the body in sync on a follow-up push instead of erroring on gh pr create.
mkdir -p .claude/.tmp/pr
cat <<'BODY' > .claude/.tmp/pr/body.md
<body content following pr.md template exactly>
BODY
git push -u origin HEAD || exit 1
if gh pr view --json number >/dev/null 2>&1; then
gh pr edit --title "<title>" --body-file .claude/.tmp/pr/body.md
else
gh pr create --title "<title>" --body-file .claude/.tmp/pr/body.md
fi
rm -rf .claude/.tmp/pr
Respond with exactly one line:
✅ PR: <url>
Do not add any other text.