git
Git commit and pull request guidelines using conventional commits. Use when creating commits, writing commit messages, creating PRs, or reviewing PR descriptions.
Security Assessment
About git
The Git skill provides comprehensive guidelines for creating Git commits and pull requests using the conventional commits format. It addresses common challenges developers face when writing commit messages and reviewing pull requests, ensuring consistency and clarity in version control practices. By adhering to these guidelines, teams can improve collaboration and maintain a clean project history, which is critical for tracking changes and understanding project evolution over time.
FAQ
What format should I use for commit messages?
Use the conventional commits format: <type>[optional scope]: <description>. Include an optional body and footer if needed.
Are there specific guidelines for pull request descriptions?
Yes, PR titles should follow the same format as commits, focusing on the 'why' and 'what' of changes without including attribution or watermarks.
What should I do if I need to mention a GitHub user?
Always verify GitHub usernames programmatically using the GitHub CLI before mentioning them in PR descriptions or comments.
Is there a preferred merge strategy for pull requests?
Yes, use regular merge commits to preserve commit history, avoiding squash or rebase options.
Can I use scope in my commit messages?
Scope is optional and should be used when it provides clarity, such as when changes are localized to a specific component or module.
Install git
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
EpicenterHQ/epicenter