git-commit

Generate conventional Git commit messages from staged changes.

Updated Apr 29, 2025
One-click install
npx skills add https://github.com/NeonTowel/oh-my-taskfiles --skill git-commit-neontowel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/NeonTowel/oh-my-taskfiles/tree/main/dotfiles/crush/skills/git-commit
Command: npx skills add https://github.com/NeonTowel/oh-my-taskfiles --skill git-commit-neontowel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates conventional Git commit messages from the current staged changes, ensuring consistency and clarity across your history.

Core Features & Use Cases

  • Automatic type and scope inference: Determine the appropriate Conventional Commits type (feat, fix, chore, etc.) and scope from staged diffs and recent history.
  • Single or multi-unit commits: Handle a single logical change or multiple distinct changes, producing ordered commits when needed.
  • Signature and guardrails: Produce a signed commit with git -S where possible and enforce imperative, descriptive messages aligned to repo style and emoji usage.

Quick Start

Stage your changes and run the git-commit skill to generate and apply a conventional commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages from staged changes?

You can generate conventional commit messages from staged changes by analyzing the staged diff and recent commit history to infer type, scope, and tone. The skill automatically applies the generated message using git commit -S.

Can I create signed git commits automatically from my staged diff?

Yes, you can create signed git commits automatically. The skill produces a signed commit using git commit -S where possible, ensuring your staged diff changes are securely recorded without altering your Git configuration.

How do I handle multiple logical changes in a single git commit?

To handle multiple logical changes in a git commit, the skill analyzes the staged diff to identify distinct units. It then produces ordered commits when needed, ensuring each logical change receives an appropriate conventional commit message.

Does the git-commit skill push changes or alter my Git configuration?

No, the git-commit skill does not push changes or alter your Git configuration. It strictly generates conventional commits from staged changes and enforces repo style, avoiding any remote updates or configuration modifications.

How does automatic type and scope inference work for conventional commits?

Automatic type and scope inference for conventional commits works by analyzing your staged diffs and the last five commits. This history allows the skill to determine the appropriate type, scope, emoji usage, and tone for your repository.