git-commit

Create descriptive git commits from staged and working-tree changes.

Updated Nov 11, 2023

Search Tags:#automation #git #workflow #commit #branching #conventional-commits

Ready to run

npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill git-commit-michaelvolz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/git-commit
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill git-commit-michaelvolz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns the messy mix of staged files, diffs, and branching indecision into a single, meaningful git commit message so you never struggle to explain the value of your work.

Core Features & Use Cases

Context-sensitive guidance: Leverages git status, diff, branch, and recent history (with remote default branch fallback) to understand what needs to be captured before writing a message.
Structured workflow enforcement: Encourages logical grouping, branch safety checks, and repository-specific conventions when staging, messaging, and verifying changes.
Use Case: When told to "commit this" or "save my changes," rely on the Skill to craft a conventional-style commit message, respect default-branch etiquette, and confirm the commit hash.

Quick Start

Use this skill to distill the current working tree into a single conventional commit message and record it.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I automate writing descriptive git commit messages?▼

Automating descriptive git commit messages involves evaluating git status, diffs, and recent history to generate a meaningful message. This process captures staged or working-tree changes while respecting repository conventions and default remote branch etiquette.

What is a conventional commit workflow and when should I use it?▼

A conventional commit workflow structures commit messages to communicate clear intent and value. You should use it when you need to capture staged changes safely, ensuring logical grouping and branch safety checks before pushing to a remote repository.

How do I create branch-aware commits before pushing changes?▼

Creating branch-aware commits requires checking the default remote branch info and recent commit patterns before staging. This ensures your changes are grouped logically and the commit message respects repository-specific conventions safely before pushing.

Can I split logical groups of changes into separate git commits automatically?▼

Splitting logical groups of changes into separate git commits is possible by evaluating the working-tree diffs. The workflow analyzes the changes to determine the right message scope, grouping related modifications together while enforcing branch safety checks.

Does this git commit automation work with existing repository conventions?▼

Yes, this git commit automation works with existing repository conventions by analyzing recent commit patterns and default remote branch info. It applies this context to determine the correct message scope and ensure the generated commit matches your project's established style.

What are the limitations of automating git commit messages?▼

Limitations of automating git commit messages include relying entirely on the quality of staged files and working-tree diffs for context. You must manually verify the suggested logical groupings and branch safety checks before confirming the commit hash and pushing.