メニュー
Create pull requests and manage the PR workflow. Use when creating a PR, reviewing PRs, managing feature branch merges, or asking about PR conventions, code review process, or the collaborative feature branch workflow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | pr-workflow |
| description | Create pull requests and manage the PR workflow. Use when creating a PR, reviewing PRs, managing feature branch merges, or asking about PR conventions, code review process, or the collaborative feature branch workflow. |
| argument-hint | PR or issue number |
| allowed-tools | ["Read","Grep","Glob","Bash(gh pr *)","Bash(gh api *)","Bash(git *)"] |
github-issues — PRs must reference an issue via Closes #<number>.claude/rules/branch-naming.md<author>/<type>/issue-<number>-<short-description>Add validation (#12)Use the PR template (.github/PULL_REQUEST_TEMPLATE.md):
gh pr create \
--title "Short descriptive title" \
--body "## Summary
Closes #<issue-number>
## Changes
- Change 1
- Change 2
## How to Test
1. Step 1
2. Step 2
## Checklist
- [x] PR is under ~400 changed lines
- [x] Branch follows naming convention
- [x] Commits reference the issue number
- [ ] Tests pass
- [ ] At least one teammate has been requested for review" \
--reviewer "teammate-username"
Closes #<number> or Fixes #<number> in the PR bodymain branch (or parent feature branch for sub-branches)When multiple people are actively coding the same feature in parallel:
mainmainIf only one person is implementing a feature, skip this — PR directly to main.
See reference.md for the git commands.
Write feature specification documents (SPEC.md). Use when creating a new feature spec, documenting feature requirements, defining feature scope and boundaries, or when the user asks to write or create a spec for a feature.
Create and manage GitHub issues following project conventions. Use when creating issues, managing issue labels, assigning issues, setting up milestones, or asking about issue conventions and requirements.
Create and manage iteration plans. Use when starting a new iteration, writing an iteration plan, breaking down requirements into tasks, planning sprint work, or asking about iteration plan format and structure.
Create iteration retrospective issues. Use when writing a retrospective, closing out an iteration, reflecting on iteration progress, or asking about retrospective format.
Best practices for writing and auditing Claude Code SKILL.md files. Use when creating a new skill, editing an existing skill, auditing skills, improving skill frontmatter, optimizing skill descriptions for auto-triggering, or asking about skill file structure, frontmatter fields, or allowed-tools configuration.