skills.rest
vertexcover-io
vertexcover-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit

Analyze git diffs and group changes into conventional commits.

4|Updated Jan 1, 2026
Search Tags:#git#planning#commit#code-quality#version-control#conventional-commits#hunk-staging
One-click install
npx skills add https://github.com/vertexcover-io/tarash --skill git-commit-vertexcover-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/vertexcover-io/tarash/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/vertexcover-io/tarash --skill git-commit-vertexcover-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps developers move beyond ad-hoc git additions by analyzing a dirty working tree, grouping related changes into logical commits, and composing conventional commit messages with appropriate prefixes (feat, fix, refactor, etc.).

Core Features & Use Cases

  • Reconnaissance and intent understanding: Inspects the repository state and diffs to infer the purpose of changes.
  • Change grouping into commits: Splits a multi-file or multi-hunk set of changes into cohesive commits, one logical concern per commit.
  • Conventional commit generation: Produces well-formed messages with proper prefixes and scopes, suitable for release notes.
  • Safe staging guidance: Recommends and performs hunk-level staging when needed, avoiding blind git add ..
  • Execution plan and guardrails: Presents a plan before applying commits and preserves user control over the final history.

Quick Start

Tell me to commit my changes, and I will propose a plan and create conventional commits using hunk-level staging.

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split multiple file changes into logical git commits?▼

To split changes into logical git commits, this workflow analyzes your working tree and groups related hunks into cohesive commits. It presents an execution plan to ensure each commit addresses a single concern before staging.

How do I generate conventional commit messages automatically?▼

To generate conventional commit messages, the workflow inspects your diffs to infer intent and composes properly prefixed messages like feat or fix. This ensures your version control history is well-documented and release-note ready.

What is the best way to avoid blind git add for staging?▼

The best way to avoid blind staging is using hunk-level staging guidance. The workflow recommends specific hunks to stage instead of executing blanket additions, preserving your control over the final repository history.

Can I review a commit plan before changes are applied to version control?▼

Yes, you can review a commit plan before changes are applied. The workflow forms a plan detailing the proposed conventional commits and staging actions, maintaining guardrails against blind execution until you approve.

Does this workflow support multi-file refactoring with conventional commits?▼

Yes, this workflow supports multi-file refactoring by analyzing changes across the entire dirty working tree. It organizes related diffs into separate commits with appropriate conventional prefixes for clear documentation.

Related Skills

Explore More Software Engineering Skills→
ian-pascoeian-pascoe
1

git-commit

Generate conventional git commit messages and stage related file changes.

Community
Advanced
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic
dotBeepsdotBeeps

commit

Create Conventional Commits with staging, scope detection, amend, and fixup workflows.

Community
Intermediate