open-skills:create-hotfix-branch
Create a new hotfix branch with an optional Gitflow prefix from an updated hotfix base branch using a task from the task tracker.
- License 许可
- MIT
- 最近更新
- 2026-10-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- open-skills:create-hotfix-branch
- description
- Create a new hotfix branch with an optional Gitflow prefix from an updated hotfix base branch using a task from the task tracker.
03 SKILL.md 正文
New Hotfix
Reply in {{response_language}}.
Use this skill to start work on a hotfix from a task reference.
- Check the worktree before changing branches. Run
git diff,git diff --cached, andgit status --short. If any tracked or untracked change exists, stop and tell the user. Do not stash, reset, or discard changes. - Check out
{{base_hotfix_branch}}and rungit pullto get its latest changes. If the branch is missing or either command fails, stop and report the error. Do not force-pull or reset the branch. - Read the user's input for a task reference. It must match the configured task regexp
{{task_prefix_regexp}}. Use the first non-empty capture group when one exists; otherwise use the full first match. If no task number was provided, the regexp is empty, or the input does not match, ask the user for a valid task reference and stop. - Use the connected task-tracker MCP tool to find the exact task. Read the task name only. Do not create, edit, transition, assign, comment on, or otherwise change the task. If the task is not found, stop and tell the user.
- Build the branch suffix from
<task number> <task name>:- Replace each run of whitespace with
-. - Remove every character except ASCII letters, digits, and
-. - Collapse repeated
-characters and trim-from both ends. - Keep the task number in the branch name.
- Replace each run of whitespace with
- If the sanitized suffix is empty, stop and report the problem. Prepend a prefix
{{hotfix_branch_prefix}}as-is to the suffix. An empty prefix adds nothing. Include any separator in the prefix, for examplehotfix/prefix yieldshotfix/ABC-123-task-namethe branch name. Do not sanitize the prefix or the joined name. - Run
git check-ref-format --branch "<branch name>"on the full name. If invalid or already exists, stop and report the problem. Otherwise create it from the updated hotfix base branch withgit checkout -b "<branch name>" "{{base_hotfix_branch}}". Pass names as literal arguments; do not evaluate shell syntax in them. - Report the created branch name and task name.
Do not commit, push, stash, reset, or modify task-tracker data.
04 同仓库更多 Skills
open-skills:track-changes
Report key changes in watched modules or files for the last day, or since Friday on Mondays, with authors and commits, in plain language.
open-skills:say-hello
A minimal test skill that greets the user.
open-skills:preview-commit
Show the change summary and proposed commit message for selected current changes without committing.
open-skills:investigate-error
Investigate crashes from a stack trace or an error-monitoring MCP reference; use diagnostic red/green tests and report evidence, root cause, impact, counts, and fix priority without applying production fixes.
open-skills:implement-task
Start implementing the current task on the current branch right away.
open-skills:explain-task
Find a task by reference through the connected MCP tracker and explain it in clear, plain language.