SKILL.md
$27
Type
Use when
feat
New functionality
fix
Broken behavior now works
ref
Behavior stays the same, structure changes
chore
Maintenance of existing tooling/config
perf
Same behavior, faster
style
Visual or formatting only
docs
Documentation only
test
Tests only
ci
CI/CD config
build
Build system
meta
Repo metadata
license
License changes
When unsure: use feat for new things, ref for restructuring, chore for maintenance.
-
Generate <type>/<short-description>.
Keep <short-description> kebab-case, ASCII-only, and ideally 3 to 6 words.
-
Choose the base without prompting:
git branch --show-current
git remote | grep -qx origin && echo origin || git remote | head -1
git symbolic-ref refs/remotes/<remote>/HEAD 2>/dev/null | sed 's|refs/remotes/<remote>/||' | tr -d '[:space:]'
- If default branch detection fails, fall back to
main, thenmaster, then the current branch
- If on a detached HEAD, branch from the current commit
- If already on a non-default branch, branch from the current branch
- Only switch to the default branch when the user explicitly asks
-
Avoid collisions by appending -2, -3, and so on until the name is unused locally and remotely.
-
Create the branch:
git checkout -b <branch-name>
Report the final branch name, but do not stop for confirmation.