メニュー
Runs the full PR workflow — creates a feature branch, commits, pushes, and opens the pull request. Use when the user asks to create or open a PR ("create a PR", "push this up and open a PR").
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ryoppippi/dotfiles --skill create-prコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Creates atomic Conventional Commits. Use when committing code changes, splitting hunks into revertable units, or writing commit messages.
Resolves missing CLI tools. Use when a command is unavailable, a shell reports command not found, or a tool must be run without installing it globally.
Runs Codex CLI for a second opinion on a decision, or as a cheap subagent for bulky work. Use before a significant approach is settled, or instead of reading pages and long output here.
SOC 職業分類に基づく
SKILL.md を表示中
| name | create-pr |
| description | Runs the full PR workflow — creates a feature branch, commits, pushes, and opens the pull request. Use when the user asks to create or open a PR ("create a PR", "push this up and open a PR"). |
Use this skill when the user asks to create or open a pull request.
A PR is a reviewable responsibility unit; one PR may contain multiple atomic commits. A branch is not a PR boundary: split independent work into separate PRs and stack only dependent work.
Inspect the current branch, status, and diff:
git status --short
git branch --show-current
git diff --stat
If the current branch is main, create a feature branch with a feature/, fix/, or chore/ prefix unless the user requested a different branch name.
Review the diff before committing. Exclude unrelated changes, temporary files, secrets, generated junk, and debug-only edits.
Commit with the repo-local commit skill using an English Conventional Commit message. When CI is unnecessary and repository instructions permit skipping it, append [ci skip] to the commit message.
Prepare a PR title and body proportional to the change:
feat, fix, docs, refactor, or chore in the PR title.--body-file - for multi-line bodies. Do not embed \n escape sequences in --body.Publish using the path that matches the PR structure:
Use gh-stack only when requested or when the branch is already stacked; verify parent-child ancestry before linking.
For an ordinary PR, push the branch and create the PR with:
git push -u origin <branch-name>
gh pr create --title "feat(scope): summary" --body-file -
Report the PR URL. If publishing fails, inspect the error and verify the branch, remote, authentication, or duplicate PR state before retrying.
All commit messages, PR titles, and PR bodies must be in English. Confirm the target branch before creating the PR, and do not call it ready until the relevant checks and review feedback have been inspected.