commit

Generate conventional git commit messages from staged and unstaged changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nxy7/streampai-elixir --skill commit-nxy7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/nxy7/streampai-elixir/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/nxy7/streampai-elixir --skill commit-nxy7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of professional git commit messages from code changes, ensuring consistency and clarity across a project.

Core Features & Use Cases

  • Analyze both staged and unstaged changes to generate a concise, descriptive commit title.
  • Support optional context to tailor messages for feature work, fixes, or refactors.
  • Output a structured body with a bullet list of changes for traceability and review.

Quick Start

Use the commit skill to generate a commit message for your current working tree. Provide optional context in the command to refine the description.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?

To generate a conventional commit message from a git diff, the Skill analyzes your staged and unstaged code changes to produce a concise title and a structured bulleted body for traceability.

What is the best way to automate git commit messages for code changes?

Automating git commit messages involves analyzing version-controlled code changes across branches to enforce a conventional commit-style format with a descriptive title and a structured body.

Can I add context to tailor automated commit messages for refactoring?

Yes, you can provide optional context during commit message generation to tailor the output specifically for feature work, bug fixes, or code refactoring tasks.

Does the commit message generator work with unstaged changes?

Yes, the commit message generator analyzes both staged and unstaged git diff outputs to ensure all current working tree modifications are captured in the final structured message.

Why use a conventional commit format for automated git messages?

Using a conventional commit format ensures project-wide consistency and clarity by separating a concise descriptive title from a structured body, improving traceability and code review processes.