Menu
Use when creating git commits to ensure consistent, clear commit messages following conventional commits format.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generic migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations
Determine feature slug interactively by auto-detecting next number and prompting user for description
Share personal documents to the shared namespace with atomic git commit and push
Use when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.
Use when documenting research findings to create properly structured research documents with frontmatter, sections, and file references.
ALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration. Guides you to use specialized agents that are more efficient than basic tools.
| name | write-commit-message |
| description | Use when creating git commits to ensure consistent, clear commit messages following conventional commits format. |
Create git commit messages following the Conventional Commits format.
See templates/commit-message.md for the full template structure, format rules, and examples.
Format:
<type>(<scope>): <subject>
[optional body]
[optional footer]
Common Types: feat, fix, docs, refactor, test, chore
Key Rules:
When user asks to commit or you're following git workflow:
git status and git diff to see changesgit commit -m "$(cat <<'EOF'
feat(auth): add JWT token refresh
Implements automatic token refresh mechanism.
EOF
)"