メニュー
Squash-merge the current PR into main, delete the branch, pull latest, and start a new feature branch. Use when the user says "merge this PR", "merge and start new branch", or is done with a PR and ready to start the next task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | merge-and-branch |
| description | Squash-merge the current PR into main, delete the branch, pull latest, and start a new feature branch. Use when the user says "merge this PR", "merge and start new branch", or is done with a PR and ready to start the next task. |
| allowed-tools | Bash(gh pr view:*), Bash(gh pr merge:*), Bash(git checkout:*), Bash(git pull:*), Bash(git branch:*), Bash(git status:*) |
I have gathered information about the current PR and git state. Here are the results:
<current_pr>
!gh pr view --json number,title,state,url,headRefName
</current_pr>
<current_branch>
!git rev-parse --abbrev-ref HEAD
</current_branch>
<git_status>
!git status --short
</git_status>
gh pr merge <number> --squash --delete-branch
git checkout main && git pull
Ask the user for the new branch name using AskUserQuestion tool.
Create the branch:
git checkout -b <branch-name>
Confirm the new branch was created with git branch --show-current.
Deep research on a technical problem using parallel subagents for web docs, Stack Overflow, and codebase exploration, saving a markdown report to brain/reference/research/. Use when the user says "research X", "investigate X", "find out how X works", or needs evidence-based recommendations before implementing.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Review current code changes by dispatching parallel specialized review agents (Vue, TypeScript, a11y, performance, security, tests). Use proactively before committing or opening a PR, or when the user asks to "review", "check", "audit", or "look over" their changes.
Inspect GitHub Actions / CI status for the current branch and plan fixes when checks fail. Use proactively after pushing, or when the user mentions "CI", "pipeline", "GitHub Actions", "failing checks", "build failing", or asks "why is CI red".
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Run ESLint across the project and fix reported errors and warnings. Use when the user asks to "lint", "fix lint errors", "run eslint", or before committing/shipping to ensure a clean lint pass.