Menu
Create a pull request from current changes. Use when the user requests PR creation, pushing changes for review, or submitting work for code review.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start implementation work with worktree isolation and cross-session file conflict avoidance. Use this skill when beginning any non-trivial code change: after plan mode, when creating a new branch, implementing features, fixing bugs across multiple files, or refactoring. Also use when the user mentions worktree, bit issue, session coordination, or parallel work.
Turn a report into a portable SVG by authoring a structured/graphical HTML layout and rendering it to SVG with satoru-render. Use when the user asks to compile, summarize, or visualize a report, or wants graphical output that stays viewable in environments that cannot render HTML (chat, PDF viewers, image-only tools, git diffs). Proactively offer SVG output whenever you produce a report that benefits from layout, charts, tables, or styling.
Plan modeで作成したプランに対して、プロジェクト特性を分析し適切なレビューエージェントを自動選択・並列起動するスキル。引数なしで実行可能。
Persist mid-session progress (plan refinements, task progress notes, scope changes, decisions, blockers) to the bit issues created by start-work. Use as a checkpoint before context compaction, after meaningful progress (multiple tasks done, plan refined, scope shifted), before pausing work, or when the user mentions 'save session', 'snapshot', 'checkpoint', 'update bit issue', or 'persist progress'.
Restore session state (plan, target files, in-flight tasks) from bit issues created by the start-work skill. Use when resuming work after Claude Code restart, when the in-memory task list is empty but bit issues exist for the current branch, or when the user mentions "restore session", "repair session", "pick up where I left off", or references a prior bit-issue-tracked session.
agent 向けテキスト指示（skill / slash command / task プロンプト / CLAUDE.md 節 / コード生成プロンプト）を、バイアスを排した実行者に動かしてもらい、両面（実行者の自己申告 + 指示側メトリクス）で評価して反復改善する手法。改善が頭打ちになるまで回す。プロンプトや skill を新規作成・大幅改訂した直後、またはエージェントの挙動が期待通りにならない原因を指示側の曖昧さに求めたいときに使う。
| name | create-pr |
| description | Create a pull request from current changes. Use when the user requests PR creation, pushing changes for review, or submitting work for code review. |
| allowed-tools | Bash(git status *), Bash(git log *), Bash(git diff *), Bash(git add *), Bash(git commit *), Bash(git push *), Bash(git checkout *), Bash(git branch *), Bash(gh pr create *), Bash(gh repo view *) |
Run in parallel:
git status -u
git diff
git diff --cached
git log --oneline -5
git branch --show-current
If on main or master, create a feature branch first:
git checkout -b <descriptive-branch-name>
git add -A to prevent accidental inclusion of sensitive files like .env):git add <file1> <file2> ...
Before pushing, verify the target repository:
gh repo view --json nameWithOwner,isFork,parent
Present to the user via AskUserQuestion:
<owner/repo><source> → <target>Wait for explicit user approval before proceeding.
git push -u origin <branch-name>
For forks, use -R <owner/repo> explicitly:
gh pr create --title "<title>" --body "<body>"
Return the PR URL to the user.
| Situation | Response |
|---|---|
| No changes to commit | Inform user, skip commit |
| On main/master | Create feature branch first |
| Push rejected | Check remote, suggest pull or ask user about force-push |
| Fork detected | Use gh pr create -R <owner/repo> to target user's repo |
| gh auth failure | Guide user to run gh auth login |