commit-message-style
Write commit messages in the preferred generic style: `type: imperative summary` with backticks around code identifiers and no scope. Use when you are about to `git commit`, splitting work into multiple commits, or when the user asks you to commit code.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Features and purpose
Write commit messages in the preferred generic style: `type: imperative summary` with backticks around code identifiers and no scope. Use when you are about to `git commit`, splitting work into multiple commits, or when the user asks you to commit code.
Quick start
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
Guides ↗Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!