メニュー
Helps rrt users create, validate, and repair semantic branch names that match their workflow. Use when starting or renaming work with `rrt branch`. DO NOT USE for arbitrary git branching conventions unrelated to rrt.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | rrt-user-branch-strategy |
| description | Helps rrt users create, validate, and repair semantic branch names that match their workflow. Use when starting or renaming work with `rrt branch`. DO NOT USE for arbitrary git branching conventions unrelated to rrt. |
I want my branch names to be predictable, policy-compliant, and fast to create.
rrt branch new feat "add release audit"
rrt branch rename --type fix "repair changelog parser"
rrt-hooks check-branch
rrt semantics| Surface | Local root | Global root |
|---|---|---|
| Claude | ./.claude | ~/.claude |
| Codex | ./.codex | ~/.codex |
| Gemini | ./.gemini | ~/.gemini |
| Copilot | ./.github | ~/.copilot |
rrt instead of ad-hoc git commandsTeaches AI assistants (Claude Code, Claude Desktop, Cursor) how to install and connect the repo-release-tools MCP server so rrt tools (config, version, health, drift, tree, artifacts, changelog, validation) are available via MCP. Use when wiring up rrt[mcp] to an AI assistant for the first time. DO NOT USE for debugging rrt CLI commands or for users who only need the CLI.
Helps rrt users bootstrap install targets, local workflow checks, and day-one automation safely. Use when setting up rrt in a new repository or workstation. DO NOT USE for repo-maintainer-only automation changes or for cloning `.claude/*` runtime assets into source control.
Helps rrt users keep `[Unreleased]` current with less manual changelog work. Use when deciding between automated and manual changelog flows with rrt hooks. DO NOT USE for maintainers redesigning changelog internals or section mapping.
Helps rrt users run local preflight checks that mirror common CI gates for branch, changelog, docs, and release readiness. Use when you want fewer CI surprises before opening a PR. DO NOT USE for editing CI pipeline internals.
Helps rrt users write conventional commits with clear intent and fewer rejected commits. Use when shaping commit messages or triaging commit lint failures. DO NOT USE for changelog authoring without a commit-quality decision.
Helps rrt users validate config files, version targets, and install paths before policy failures happen. Use when setting up or repairing rrt config. DO NOT USE for changing internal config loader implementation.