git-commit-guidelines
Git Commit Guidelines
Best practices for writing clear, consistent git commit messages.
When to Apply
Reference these guidelines when:
- Writing commit messages
- Reviewing pull requests for commit quality
- Setting up commit conventions for a new project
Rules
| Rule | Summary |
|---|---|
structure |
Use subject line + blank line + body format |
subject-line |
Keep subject under 72 chars, imperative mood, no trailing period |
body |
Explain what and why, not how |
scope |
One logical change per commit |
More from roin-orca/agent-skills
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Transforms vague ideas into validated, actionable designs through structured collaborative dialogue.
0brainstormingv2
You MUST use this before any creative work — designing features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design through structured collaborative dialogue before any implementation begins.
0json-tools
Helps with common JSON file tasks: formatting, validating, diffing, transforming, querying, and fixing malformed JSON. Use when the user asks to work with JSON data or .json files.
0brainstorm
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
0brainstormingv3
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
0