メニュー
Create or update a pull request with a terse semantic title and appropriate description. Use when creating a PR, opening a pull request, updating PR description, or when a PR already exists and the description should be checked and updated.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | open-pr |
| description | Create or update a pull request with a terse semantic title and appropriate description. Use when creating a PR, opening a pull request, updating PR description, or when a PR already exists and the description should be checked and updated. |
Create a new PR with a terse semantic title and body matching the project template, or—if a PR already exists for the branch—check and update the PR description (and title if needed).
gh) installed and authenticated (gh auth status).Same convention as commit messages: <type>(<scope>): <description>. Semantic, terse (under 50 chars), imperative. See CONTRIBUTING.md and AGENTS.md.
Align with .github/pull_request_template.md: Description, Type of Change, Changes Made, Testing, Checklist, Related Issues. Fill from the branch's commits and diff.
gh pr view / gh pr list --head <branch>). If a PR exists, use Update flow instead.gh pr create --title "..." --body "..." (or --body-file).gh pr view for title and body).gh pr edit --body "..." and optionally --title "...".Only update when description or title is inaccurate or incomplete.
gh auth.gh): installed and authenticated (gh auth status). If gh is not available, instruct the user to install and authenticate.Use this skill when writing code, implementing features, refactoring, planning architecture, designing systems, reviewing code, or debugging. This skill transforms junior-level code into senior-engineer quality software through SOLID principles, TDD, clean code practices, and professional software design.
Resolve git rebase conflicts: when to accept main's version vs branch, how to remove conflict markers, and how to avoid duplicate sections. Use when resolving conflicts during git rebase (e.g. rebase onto main) or when continuing a rebase after fixing conflicts.
When adding new API or server routes: document manual validation, add an automated check (smoke or test) that hits the route, wire it into the suite, and run that verification before marking the task complete. Use when adding new Nuxt/API routes, server endpoints, or similar.
Finish and ship work: sync task systems (taskmaster/beads if in use), ensure quality gates pass, run deslop, then shipit. Use when wrapping up a branch—closing tasks, cleaning AI slop, and opening or updating a PR.
Group and stage related changes for git commit. Use when staging files for commit, grouping related changes, or deciding what to include in each commit. Implements how to group changes and when to split commits.
Write semantic commit messages in Conventional Commits format. Use when committing, writing commit messages, or when a terse semantic commit is required. Covers format, types, scope, imperative mood, and length.