git-commit

Generate conventional git commit messages using type(scope): description format.

6|Updated Jan 29, 2023

Search Tags:#git #workflow #commit #cli #version-control #conventional-commits

Ready to run

npx skills add https://github.com/rethinkhealth/glion --skill git-commit-rethinkhealth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/rethinkhealth/glion --skill git-commit-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create clear, conventional git commit messages for changes in the working tree, improving history readability and collaboration.

Core Features & Use Cases

Conventional messaging: suggests and formats messages as type(scope): description based on project conventions or defaults.
Context-aware workflow: guides gathering repo state, determining conventions, and splitting changes into logical commits when needed.
Safe staging guidance: helps stage only intended changes and verifies there are changes before committing.

Quick Start

Stage your changes and run the commit workflow to produce a conventional, well-formatted message.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I write conventional commit messages for staged and unstaged changes?▼

Conventional commit messages follow a type(scope): description format to clarify change intent. This skill analyzes your working tree state and formats commits accordingly, whether changes are staged or unstaged.

What is the conventional commits format and how does it apply to my git workflow?▼

The conventional commits format structures messages as type(scope): description to improve history readability. It applies to your git workflow by guiding staging, determining project conventions, and optionally splitting changes into logical commits.

Can I use this to commit unstaged changes without a predefined project convention?▼

Yes, this skill supports projects without predefined conventions by applying default conventional commit rules. It gathers repository state, helps stage only intended changes, and verifies there are changes before committing.

What's the best way to split logical changes into separate git commits?▼

Splitting logical changes requires analyzing the working tree to identify distinct modifications. This context-aware workflow helps stage only intended changes and formats each logical split into a conventional commit message.

Does this git commit workflow support both staged and unstaged working tree changes?▼

Yes, this git commit workflow supports both staged and unstaged changes in the working tree. It uses git commands to gather context, guides safe staging, and enforces conventional commit formatting before performing commits.