git-commit

Generate Conventional Commits from git diffs with type, scope, and description.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill git-commit-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/selfagency/agentsy --skill git-commit-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork of writing Conventional Commits by analyzing your current changes and producing a standardized commit type, scope, and message so your project history stays consistent.

Core Features & Use Cases

  • Conventional message generation: Infers the correct type and optional scope, then drafts a concise description from the diff.
  • Intelligent staging: Helps you stage changes thoughtfully (including interactive staging) so each commit represents a logical unit.
  • Interactive commit workflow: Lets you confirm or override type/scope/description before running the commit, supporting cases like “make this change a feat instead of a fix.”

Example use case: You changed both a small bug in a component and updated documentation; use the diff analysis and staging guidance to create separate, correctly labeled commits (fix(scope): ... and docs(scope): ...).

Quick Start

Tell the assistant to analyze your diff and create a conventional commit message, then guide you through staging and committing with that message.

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

Conventional commit generation analyzes your git diff to infer the correct type, optional scope, and description, proposing a standardized commit message for your project history.

Can I override the inferred commit type and scope before executing git commit?

Yes, the interactive commit workflow lets you confirm or override the proposed type, scope, and description before executing the commit, allowing changes like switching a fix to a feat.

How do I stage changes logically so each commit represents a single unit of work?

Intelligent staging analyzes your git diff and provides interactive staging guidance, helping you separate distinct changes like bug fixes and documentation into individual, correctly labeled commits.

What is the best way to automate conventional commits for mixed code and documentation changes?

Automating conventional commits for mixed changes uses diff analysis to separate logical units, generating distinct standardized messages like fix(scope) and docs(scope) for each staged change set.

Does this commit message generator support refactors, tests, and CI configuration changes?

Yes, conventional commit generation applies to developer workflows creating commits from code, documentation, CI configuration, refactors, tests, and other logical change sets.