About git-commit
A skill for creating Git commits in Conventional Commits format, with project-specific rules for scope, subject wording, and focused changes. It is intended for contributors who want commit messages to follow documented conventions.
Key features
- 01Conventional Commits formatting
- 02Required kebab-case scope
- 03Imperative subject under 50 characters
- 04Multi-line commit examples
- 05Project convention check
Use cases
- 01Writing a scoped feature commit
- 02Recording a security fix
- 03Grouping related changes in one commit
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ fvadicamo/ dev-agent-skills --skill git-commitAfter installing, type/git-commitin Claude Code to confirm it loaded.
Bundled filesreferences/commit_examples.md
Details
From the project READMEGit commit
Creates git commits following Conventional Commits format.
Recent project commits
!git log --oneline -5 2>/dev/null
Quick start
# 1. Stage changes
git add <files>
# 2. Create commit
git commit -m "type(scope): subject"
Project conventions
- Scope is required (kebab-case):
validation,auth,cookie-service,api - Additional type beyond standard CC:
security(vulnerability fixes or hardening) - HEREDOC for multi-line commits:
git commit -m "$(cat <<'EOF'
feat(validation): add URLValidator with domain whitelist
Implement URLValidator class supporting:
- Domain whitelist enforcement
- Dangerous scheme blocking
Addresses Requirement 31
Part of Task 5.1
EOF
)"
Important rules
- ALWAYS check CLAUDE.md conventions first - use project format if it differs
- ALWAYS include scope in parentheses
- ALWAYS use present tense imperative verb for the subject
- NEVER end subject with a period
- NEVER exceed 50 chars in the subject line
- NEVER use generic messages ("update code", "fix bug", "changes")
- Group related changes into a single focused commit
References
references/commit_examples.md- Extended examples by type, good/bad comparisons
Comments
Markdown supported