git-commit

Create conventional git commits from working tree changes.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill git-commit-udecode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/udecode/kitcn --skill git-commit-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides the user to create well-structured commits that convey intent and follow project conventions, with guardrails for branch management and safe staging.

Core Features & Use Cases

  • Guarded commit creation: ensures commits include only intended changes and follow conventional formats.
  • Branch and staging workflows: prompts for branch creation when detached HEAD and stages targeted files safely.
  • Use Case: Imagine you are finishing a feature; use this skill to generate a clean commit message and organize changes into a feature branch.

Quick Start

Provide a well-formed commit message for your current changes following this Skill.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create conventional commits from my current working tree changes?

To create conventional commits from your working tree changes, this skill analyzes staged files, derives the appropriate type and scope from the modifications, and generates a well-structured commit message with a clear rationale.

What is the best way to stage targeted files safely for a git commit?

The best way to stage targeted files safely is to use a skill that applies guardrails to your workflow, ensuring only intended modifications are staged before generating a structured commit message.

How does branch creation work when committing in a detached HEAD state?

When committing in a detached HEAD state, this skill prompts for clean branch creation to ensure your changes are safely tracked on a valid branch before staging and committing.

Why should I include a rationale in my conventional commit messages?

Including a rationale in conventional commit messages conveys the intent behind your changes, helping teams understand the context and reasoning of the modifications rather than just the technical details.

Can I use this git workflow skill without any external dependencies?

Yes, you can use this git workflow skill without external dependencies as it operates independently to parse your working tree, manage staging, and format your commit messages.

What are the limitations of automating git commit message generation from code changes?

Automating git commit message generation relies entirely on the changes present in your working tree, meaning it cannot infer external context or unstaged decisions not reflected in the actual file modifications.