git-commit

Draft Conventional Commit messages from staged and unstaged diffs.

8|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/narumiruna/skills --skill git-commit-narumiruna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/narumiruna/skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/narumiruna/skills --skill git-commit-narumiruna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Draft concise Conventional Commit messages directly from code changes, ensuring consistent history and clearer project trails.

Core Features & Use Cases

  • Analyze the current diff (staged and unstaged) to identify changed files and intended intent.
  • Suggest a Conventional Commits type and optional scope based on the changes.
  • Output a correctly formatted commit title, with optional body and trailers, ready for git commit.

Quick Start

Draft a Conventional Commit message from the current diff.

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 my git diff?

Generate conventional commit messages by analyzing your working directory and staged diffs to identify changed files, determine the appropriate type and scope, and format a compliant commit title with an optional body.

What is the best way to write a conventional commit title with an ambiguous change type?

When the change type is ambiguous, validate the commit message against the conventional commits specification to ensure the correct type, scope, and breaking-change wording are applied before finalizing the title.

Can I draft a git commit message from both staged and unstaged changes?

Yes, you can draft a git commit message from both staged and unstaged changes; the tool analyzes the current diff to identify changed files and infer the intended commit type and scope.

How do I format breaking changes and trailers in a conventional commit?

Format breaking changes and trailers by validating the wording against the conventional commits specification, ensuring the commit body correctly flags breaking changes and appends necessary metadata trailers.

Does this conventional commits workflow require any external dependencies?

No, this conventional commits workflow requires no external dependencies, allowing you to directly draft precise commit messages from your code changes without installing additional tools.