Codebelt

Git Visual Commits

A commit orchestration skill for teams that want commit quality and attribution treated as part of the workflow.

Git · Releases · Automation 10 installs Git worktrees Commit authorship CLI agents IDE agents
Open on Skills.sh View source

Overview

Git Visual Commits treats committing as a structured engineering task, not the last hurried step before pushing. It reviews the worktree, groups changes semantically, picks the right identity mode, composes an emoji-first subject, and verifies that the stored author and commit body match the intended workflow.

The skill is especially strong when a repository wants consistent commit language and clear authorship boundaries between human, bot, and collaborative changes.

Concepts

  • Identity-aware execution: git bot commit, git commit, and git our commit are separate operating modes with different attribution rules.
  • Semantic grouping first: the full worktree is analyzed and split into logical commits instead of being flattened into one umbrella change.
  • Reference-backed wording: emoji and optional prefix choices are validated against the bundled commit-language reference.
  • Post-commit verification: the commit is not considered done until author and message body were read back from git and confirmed.

Usage guidance

Use this skill whenever the user asks to commit changes, review commit scope, or decide what should be grouped together. It is ideal for repositories where attribution, commit readability, and semantic history matter as much as the code change itself.

Let it inspect the full worktree unless the user explicitly narrows the scope. The strongest outcomes come when the skill is allowed to plan the commits first and only execute after the identity mode and grouping are clear.