Skill

git-commits

Enforces git commit best practices with conventional commits format, atomic principles, type prefixes, and semantic versioning for clear, meaningful history. Use when committing code.

Git

git-workflow

npx claudepluginhub jpoutrin/product-forge --plugin git-workflow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This skill enforces git commit best practices and conventional commits format.

SKILL.md

Similar Skills

conventional-commits

586

Formats Git commit messages according to Conventional Commits spec with types like feat/fix, scopes, bodies, and breaking changes. Enables automated changelogs and semantic versioning. Activates on commit writing or git mentions.

sundial-org-awesome-openclaw-skills-4

conventional-commits

Guides Git commit messages to follow Conventional Commits v1.0.0 spec, covering types (feat, fix, refactor, etc.), scopes, structure, body, footers, and examples. Use for code commits and PR reviews.

1 file

conventional-commits

Writes, reviews, and validates git commit messages following Conventional Commits v1.0.0. Helps select types (feat/fix/etc), mark breaking changes, format multi-line commits, and map to SemVer bumps.

1 tool

ts-dev-kit

Stats

Parent Repo Stars10

Parent Repo Forks1

Last CommitFeb 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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:

Represent ONE logical change
Be independently revertible
Pass all tests
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

Type is required and lowercase
Description starts lowercase, no period
Imperative mood: "add" not "added" or "adds"
First line under 72 characters
Body wraps at 72 characters
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>