commit
Git Commit Command
Security Assessment
About commit
The 'commit' skill is designed to streamline the process of creating Git commits while adhering to project conventions. It ensures that the commit process follows a structured workflow, which includes running tests, staging files individually, reviewing changes, and following specific commit message rules. By automating and enforcing these best practices, it helps teams maintain consistent code quality and documentation in their version control history.
FAQ
How should I use the 'commit' skill?
When using this skill, announce to the user: 'Using /commit skill to create a commit.' The skill guides you through the process of staging files, reviewing changes, and committing using specific message formatting rules.
What are the requirements for using this skill?
Before using the skill, ensure that project tests are run (except for documentation-only changes), and files are staged individually using Git. Avoid using commands like 'git add .' or 'git add -A'.
What are the rules for writing commit messages?
Commit messages must be written in English, using the imperative mood (e.g., 'Fix' instead of 'Fixed'). The subject line should start with an emoji code and should not end with a period. The body should be concise, describing what and why the change was made, limited to 2-3 bullet points.
Can I use this skill for documentation changes?
Yes, the skill allows skipping project tests for documentation-only changes, making it easy to commit those without additional requirements.
Install commit
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
sakuro/dotfiles