git-commit

Create a conventional git commit from staged or unstaged changes.

Updated Sep 16, 2025

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

Ready to run

npx skills add https://github.com/mukles/platejs-markdown-converter --skill git-commit-mukles

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a single, well-crafted git commit from the current working tree changes to ensure clarity and alignment with repo conventions when present.

Core Features & Use Cases

Generates well-structured commit messages that follow repo conventions when they exist, or falls back to conventional commits.
Handles both staged and unstaged changes and suggests or creates a feature branch if needed, with guidance on selective staging to avoid sensitive files.
Guides the user through branch handling (detached HEAD vs on-branch) and provides safe, incremental staging and commit steps.

Quick Start

Tell me to commit your changes and I will generate a well-formed conventional commit message and apply it to your working tree.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate a conventional commit message from staged and unstaged changes?▼

To generate a conventional commit message, the Skill analyzes your current working tree, detects repo-specific conventions or recent history, selectively stages files, and applies a properly formatted commit using a heredoc.

What's the best way to handle a git commit in a detached HEAD state?▼

Handling a git commit in a detached HEAD state requires safe branch management; the Skill guides you through creating or switching to a feature branch before staging files and applying the commit to preserve your history.

How do I avoid committing sensitive files when staging changes for a git commit?▼

To avoid committing sensitive files during a git commit, the Skill provides guidance on selective staging, allowing you to review and choose specific files from your working tree rather than committing everything blindly.

Does this git commit tool follow existing repo conventions or default to standard conventional commits?▼

The git commit tool first checks for repo-specific commit conventions, then falls back to analyzing your recent commit history, and finally defaults to standard conventional commits to ensure properly formatted messages.

Why does my git workflow need a feature branch before creating a commit?▼

Your git workflow needs a feature branch before creating a commit to ensure safe branch handling; the Skill suggests creating one if you are in a detached HEAD state or lack an active branch to receive the staged changes.

Can I automate creating a single git commit from multiple unstaged changes?▼

Yes, you can automate creating a single git commit from unstaged changes; the Skill manages the entire working tree, stages files selectively, and generates one well-structured commit message aligned with your version-control conventions.