Can this skill handle project-specific rules?

Yes, it automatically scans for CLAUDE.md or .kiro files to identify and apply any custom commit conventions specific to your repository.

How does it handle breaking changes?

It follows the specification by adding a '!' after the scope or including a 'BREAKING CHANGE:' footer, which triggers major version bumps in automated tools.

What is the Conventional Commits format?

It is a lightweight convention on top of commit messages that provides a set of rules for creating an explicit commit history (e.g., 'feat(auth): add login').

Is it compatible with GitHub Pull Requests?

Yes, it integrates with PR creation workflows by extracting commit types for labels and using commit bodies to build comprehensive PR summaries.

Does it prevent committing secrets?

The skill includes built-in logic to block the staging of sensitive files like .env, credentials.json, and large binaries without explicit approval.

Conventional Git Commits

Name: Conventional Git Commits
Author: fvadicamo

byfvadicamo

•

Developer Tools

Automates the creation of standardized, high-quality Git commits following the Conventional Commits specification.

About

The Git Commit skill streamlines version control workflows by enforcing the Conventional Commits standard across your development process. It intelligently identifies project-specific conventions from configuration files like CLAUDE.md, guides users through staging files, and constructs structured commit messages with appropriate types, scopes, and descriptive subjects. By automating the formatting of branch updates and PR closures, it ensures a clean, searchable, and machine-readable git history that integrates seamlessly with automated release tools and semantic versioning systems.

Key Features

Provides built-in safeguards to prevent committing secrets, .env files, or credentials.
Enforces Conventional Commits format with type, scope, and subject line rules.
Generates extended descriptions for Pull Request closures and merge commits.
Supports multi-line commit bodies, Git trailers, and breaking change indicators.
28 GitHub stars
Automatically detects and respects project-specific conventions from CLAUDE.md.

Use Cases

Cleaning up staging areas and creating focused, atomic commits from complex code changes.
Ensuring every commit follows project-specific naming conventions and architectural scopes.
Standardizing repository history for teams using semantic versioning and automated changelogs.

About

Key Features

Provides built-in safeguards to prevent committing secrets, .env files, or credentials.
Enforces Conventional Commits format with type, scope, and subject line rules.
Generates extended descriptions for Pull Request closures and merge commits.
Supports multi-line commit bodies, Git trailers, and breaking change indicators.
28 GitHub stars
Automatically detects and respects project-specific conventions from CLAUDE.md.

Use Cases

Cleaning up staging areas and creating focused, atomic commits from complex code changes.
Ensuring every commit follows project-specific naming conventions and architectural scopes.
Standardizing repository history for teams using semantic versioning and automated changelogs.