Use for /pr, or 'create a PR' / 'open a pull request' — creates a pull request for the current branch against the repo's base branch with a formatted title and body. Not for reviewing an existing PR (review-pr).
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Create a pull request for current branch targeting the repo's base branch.
User says: "/pr", "create a PR", "open a pull request", "push this up for review", or the current branch is ready to be reviewed against the base branch.
Not this: reviewing an existing PR → /review-pr.
The Git and GitHub mechanics are deterministic and run inline. The main loop keeps only the judgment work: summarize the diff, draft the review text, and show the exact title/body before the external PR creation.
egregore.json → repos[]), create the PR there. Otherwise use the hub.bash bin/base-branch.sh
bash bin/base-branch.sh <repo-name>.
A non-zero exit means the configuration could not be resolved: stop before any
Git change. Use the printed name wherever {base} appears below..claude/context/pr-format.md:
type(scope): imperative summary (≤ 72 chars) — the same
grammar as commit subjects (.claude/context/commit-format.md).
A single-commit PR reuses its commit subject verbatim when it
describes the whole PR.## What (1–4 bullets) · ## Why (1–3 sentences) ·
## Verification (how it was checked — required when the diff touches
non-markdown files; be honest if unverified) · ## Risk / ## Links
when real · attribution footer of the harness that authored the body
(final non-blank line, e.g. 🤖 Generated with [Claude Code](https://claude.com/claude-code))gh pr create --base "{base}" --title "$TITLE" --body "$BODY" — never --fill, never an empty body (the pr-format CI check fails bare PRs)bash bin/graph-op.sh record-pr <number> "<title>" 2>/dev/null &
<number> comes from the gh pr create output URL; the command resolves
the session, repository, and author itself./pr means "please review this"> /pr
Creating pull request...
Branch: feature/2026-01-20-mcp-authentication
Base: main
Commits: 3 commits ahead of main
Changes: +78 lines, -5 lines, 3 files
Title: feat(mcp): add API key authentication
(from your last commit — edit? y/n)
> n
Description — summarize what this PR does:
> Adds API key validation to MCP server. Keys are checked against env var. Includes tests.
Creating PR via GitHub CLI...
gh pr create --base main --title "..."
✓ PR #42 created: https://github.com/{github_org}/myapp/pull/42
PR targeting main — ready for review.
Share the PR link. Run /handoff if ending your session.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
日本語の概要は準備中です。原文の説明を表示しています。
Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.
日本語の概要は準備中です。原文の説明を表示しています。
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
日本語の概要は準備中です。原文の説明を表示しています。
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
日本語の概要は準備中です。原文の説明を表示しています。
Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
日本語の概要は準備中です。原文の説明を表示しています。