メニュー
Ensure we're on a feature or bug branch. If current branch is mainline (main, master, dev) or a release branch (release/*), create and checkout a new branch. Use when a workflow or user request should avoid committing or pushing directly to mainline or release.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | ensure-feature-branch |
| description | Ensure we're on a feature or bug branch. If current branch is mainline (main, master, dev) or a release branch (release/*), create and checkout a new branch. Use when a workflow or user request should avoid committing or pushing directly to mainline or release. |
Ensure the current branch is a feature or bug branch. If it is a mainline or release branch, create and checkout a new branch so commits are not made on mainline/release. Use this skill on its own or as part of any automation (e.g. pre-commit hook, command, or manual request).
Treat these as not feature/bug branches; create a new branch if current branch is one of:
main, master, devrelease/* (e.g. release/1.0, release/2.x)Repos may use different default branch names (e.g. trunk, development). If the repo clearly uses another name as the primary integration branch, treat it as mainline.
git branch --show-currentfeat/<description> for features or fix/<description> for fixes. If the change type is unclear, use feat/<description> or a neutral chore/<description>.git checkout -b <branch-name>feat/..., fix/..., or any branch not mainline/release), do nothing and proceed.feat/xyz or an updatecli branch).