When does the skill choose to squash instead of creating a new commit?

It defaults to the Squash strategy (commit --amend) when the current changes relate to the same theme or function as the existing commit on the branch.

Does this skill support Conventional Commits?

Yes, it follows the Conventional Commits format, utilizing standardized types such as feat, fix, refactor, and chore to ensure clear history.

Can this skill help with interactive rebasing?

Yes, it provides specific guidance for using interactive rebase to reorganize, merge, or reword multiple commits into a logical sequence.

Does it prevent committing to the main branch?

Yes, one of the core safety instructions is to avoid running commit commands directly on the main branch to protect project stability.

High Quality Git Commits

Name: High Quality Git Commits
Author: AKABANAKK

byAKABANAKK

Developer Tools

Streamlines Git commit workflows by enforcing logical history, atomic changes, and conventional commit standards.

About

The High Quality Commit skill provides Claude with a structured framework for managing Git history effectively within a development environment. It guides the AI to intelligently choose between squashing changes into existing commits, creating new atomic commits, or performing interactive rebases to maintain a clean and readable project timeline. By following standardized message formats and assessing branch state before every action, this skill ensures that version control remains organized, professional, and easy to audit for any size development team.

Key Features

Automated commit strategy selection based on branch context
Interactive rebase guidance for logical history reorganization
Prevention of direct commits to the main branch
0 GitHub stars
Atomic commit verification with post-action status checks
Strict enforcement of Conventional Commit message standards

Use Cases

Refactoring messy local work into logical, atomic commits
Implementing consistent commit message styles across a team
Standardizing commit history before submitting a pull request

About

Key Features

Automated commit strategy selection based on branch context
Interactive rebase guidance for logical history reorganization
Prevention of direct commits to the main branch
0 GitHub stars
Atomic commit verification with post-action status checks
Strict enforcement of Conventional Commit message standards

Use Cases

Refactoring messy local work into logical, atomic commits
Implementing consistent commit message styles across a team
Standardizing commit history before submitting a pull request