Is it safe to use on the main branch?

The skill includes specific safeguards and warnings to discourage direct commits to the main branch, protecting your project's primary branch stability.

How does it decide between squashing and a new commit?

It evaluates whether the current changes relate to the previous commit's theme; if they are part of the same logical task, it recommends an amend or squash to keep history concise.

Does this skill automatically push my changes?

No, this skill focuses on creating and organizing high-quality local commits. You maintain full control over when to push your changes to remote repositories.

Can it help me follow Conventional Commits?

Yes, the skill includes strict guidelines for commit message types such as feat, fix, and refactor, ensuring your project history follows industry standards.

High Quality Git Commit

Name: High Quality Git Commit
Author: getty104

bygetty104

•

Developer Tools

Automates professional Git commit workflows using squash and rebase strategies to maintain a clean and logical repository history.

About

This skill empowers Claude to act as an expert Git maintainer, ensuring every code change is recorded with precision and clarity. It guides the AI through a sophisticated decision-making process—checking branch status, selecting between squashing into existing commits, creating new entries, or performing interactive rebases—to ensure the commit log remains readable and professional. By enforcing Conventional Commit standards and logical history restructuring, it helps developers maintain production-grade repositories with minimal manual effort.

Key Features

Interactive rebase guidance for logical history restructuring
Automated enforcement of Conventional Commit message standards
Pre-commit branch status and log validation
Context-aware commit strategy selection (Squash vs. New vs. Rebase)
3 GitHub stars
Atomic commit enforcement to ensure independent, meaningful changes

Use Cases

Cleaning up multiple small 'work in progress' commits into a single logical feature commit
Refactoring local commit history before submitting a pull request for review
Automating the generation of high-quality commit messages following industry best practices

About

Key Features

Interactive rebase guidance for logical history restructuring
Automated enforcement of Conventional Commit message standards
Pre-commit branch status and log validation
Context-aware commit strategy selection (Squash vs. New vs. Rebase)
3 GitHub stars
Atomic commit enforcement to ensure independent, meaningful changes

Use Cases

Cleaning up multiple small 'work in progress' commits into a single logical feature commit
Refactoring local commit history before submitting a pull request for review
Automating the generation of high-quality commit messages following industry best practices