git-commits
Git commit best practices with conventional commits format and atomic commit principles. Use when committing code to ensure clear, meaningful commit history with proper type prefixes and semantic versioning support.
Best use case
git-commits is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Git commit best practices with conventional commits format and atomic commit principles. Use when committing code to ensure clear, meaningful commit history with proper type prefixes and semantic versioning support.
Teams using git-commits should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-commits/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-commits Compares
| Feature / Agent | git-commits | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Git commit best practices with conventional commits format and atomic commit principles. Use when committing code to ensure clear, meaningful commit history with proper type prefixes and semantic versioning support.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Git Commits Skill This skill enforces git commit best practices and conventional commits format. ## Conventional Commits Format ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` ## Commit Types | Type | Description | Semver | |------|-------------|--------| | `feat` | New feature | MINOR | | `fix` | Bug fix | PATCH | | `docs` | Documentation only | - | | `style` | Formatting, no code change | - | | `refactor` | Code restructuring | - | | `perf` | Performance improvement | PATCH | | `test` | Adding tests | - | | `chore` | Maintenance tasks | - | | `ci` | CI configuration | - | | `build` | Build system changes | - | ## Examples ### Feature ``` feat(auth): add OAuth2 login support Implement OAuth2 flow with Google and GitHub providers. Includes token refresh and secure storage. Closes #123 ``` ### Bug Fix ``` fix(api): handle null response in user endpoint The /users endpoint crashed when the database returned null. Added proper null checking and error response. ``` ### Breaking Change ``` feat(api)!: change response format for /users endpoint BREAKING CHANGE: Response now returns array instead of object. Migration guide available in docs/migrations/v2.md ``` ## Atomic Commits Each commit should: 1. Represent ONE logical change 2. Be independently revertible 3. Pass all tests 4. Be complete (not "WIP") ### Bad Example ``` git commit -m "Fix bugs and add features and update docs" ``` ### Good Example ``` git commit -m "fix(auth): prevent session timeout on refresh" git commit -m "feat(dashboard): add export to CSV button" git commit -m "docs(api): update authentication examples" ``` ## Commit Message Rules 1. **Type is required** and lowercase 2. **Description** starts lowercase, no period 3. **Imperative mood**: "add" not "added" or "adds" 4. **First line** under 72 characters 5. **Body** wraps at 72 characters 6. **Breaking changes** marked with `!` or footer ## Claude Code Commit Footer When committing with Claude Code, include: ``` 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> ```
Related Skills
zod
Zod schema validation patterns and type inference. Auto-loads when validating schemas, parsing data, validating forms, checking types at runtime, or using z.object/z.string/z.infer in TypeScript.
typescript-import-style
Merge-friendly import formatting (one-per-line, alphabetical). Auto-loads when writing TypeScript/JavaScript imports to minimize merge conflicts in parallel development. Enforces consistent grouping and sorting.
setup-mcp-auth
Configure authentication for an existing FastMCP server
fastmcp
FastMCP TypeScript framework patterns for MCP servers. Auto-loads when building MCP servers, creating tools/resources/prompts, implementing authentication, configuring transports, or working with FastMCP in TypeScript.
add-mcp-tool
Add a new tool to an existing FastMCP server with guided configuration
add-mcp-resource
Add a new resource or resource template to an existing FastMCP server
plan-with-team
Validate plan file ownership
privacy-compliance
GDPR, CCPA, and privacy compliance guidance for data protection. Use when handling personal data, implementing consent management, or ensuring regulatory compliance across jurisdictions.
oauth
OAuth 2.0 and OpenID Connect implementation patterns. Use when implementing authentication, authorization flows, or integrating with OAuth providers like Google, GitHub, or custom identity providers.
mcp-security
Use when securing MCP servers, preventing prompt injection, implementing authorization, validating user input, or building secure multi-agent pipelines. Provides 5-layer defense architecture patterns.
rag-cag-security
Security patterns for RAG and CAG systems with multi-tenant isolation. Use when building retrieval-augmented or cache-augmented generation systems that require tenant isolation, access control, and secure data handling.
chunking-strategies
Document chunking strategies for RAG systems. Use when implementing document processing pipelines to determine optimal chunking approaches based on document type and retrieval requirements.