メニュー
Create a GitHub pull request targeting main, with body auto-generated from the diff, using this repo's PR template. Use when the user wants to open a PR from the current branch.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/sefop/sefop-python-starter --skill create-prコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Audit a repo for inconsistencies — stale docs, naming drift, structural asymmetry, test drift — and produce a tiered report, then grill the user on what to fix. Use when the user wants an inconsistency/consistency audit, asks to find contradictions or drift in a codebase, or wants confusing docs/code mismatches surfaced.
Commenting code conventions for this project. Use when writing or reviewing any Python code in this repo.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
SOC 職業分類に基づく
SKILL.md を表示中
| name | create-pr |
| description | Create a GitHub pull request targeting main, with body auto-generated from the diff, using this repo's PR template. Use when the user wants to open a PR from the current branch. |
Create a pull request for the current branch targeting main. Follow these steps exactly:
Gather context — run these commands in parallel:
git log main..HEAD --oneline — list commits on this branchgit diff main...HEAD --stat — summarize changed filesgit diff main...HEAD — full diff (use to understand the changes)git branch --show-current — current branch nameCheck push status — run git status -sb to see if the branch has an upstream. If no upstream is set, ask the user: "Branch <name> hasn't been pushed yet. Push it now?" — wait for confirmation before running git push -u origin <branch>.
Detect appropriate labels — analyze the changes to determine relevant labels:
documentation — if changes are in .md files, docs/, or .github/bug — if commit messages contain "fix", "bug", or "issue"enhancement — if new files or features are addedtesting — if changes are in test files or add new testsGenerate PR title — derive a concise title (under 70 chars) from the commits and diff. Focus on the "what changed at a high level", not implementation details.
Generate PR body — fill in this repo's template using the git context. Every section must be answered:
# What problem did you solve?
<Explain the motivation — the bug, gap, or need this PR addresses. 1-3 sentences.>
# Describe the changes
<Summarize the main code changes. Keep it simple — what was added, removed, or restructured. Bullet points preferred.>
# Testing
<Describe how the changes were tested — unit tests added/run, manual steps taken, CLI commands used.>
gh pr create --title "<title>" --base main --label "<label1>" --label "<label2>" --body "$(cat <<'EOF'
<body>
EOF
)"
(Include --label flags only for detected labels)
gh pr create.