commit

Generate a Conventional Commits message and create a git commit from working tree changes.

Updated May 11, 2022

Search Tags:#git #developer workflow #conventional commits #commit message generation #staging changes #history-aware writing

Ready to run

npx skills add https://github.com/Namacha411/dotfiles --skill commit-namacha411

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Namacha411/dotfiles/tree/main/shared/claude/skills/commit
Command: npx skills add https://github.com/Namacha411/dotfiles --skill commit-namacha411

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the hassle of writing thoughtful, consistent Git commit messages by guiding you through staging and generating a Conventional Commits format using recent diff and history.

Core Features & Use Cases

Guided commit context: Collects git status, diff, and the last 10 commits to match existing tone and scope conventions.
Selective staging safety: Shows modified/staged/untracked files and asks you to confirm exactly which ones to include.
Conventional Commits generation: Produces a Conventional Commits subject (and an optional wrapped body) and then commits with a co-author attribution.

Quick Start

Tell the AI to commit your current changes using the commit skill.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate Conventional Commits messages from staged and unstaged git changes?▼

You can generate Conventional Commits messages by having the skill collect your git status, diff, and recent history. It confirms your file selection, stages files explicitly, and produces a valid commit subject and optional body.

Can I selectively stage modified and untracked files before creating a git commit?▼

Yes, you can selectively stage files before creating a git commit. The skill displays modified, staged, and untracked files, asks you to confirm exactly which ones to include, and stages them explicitly per filename.

What is the best way to match existing commit message tone and scope conventions in git?▼

The best way to match existing commit tone and scope conventions is to analyze recent repository history. The skill collects the last 10 commits to ensure your newly generated Conventional Commits align with established project patterns.

Does generating Conventional Commits require manually writing the commit body?▼

No, generating Conventional Commits does not require manually writing the commit body. The skill automatically produces a valid Conventional Commits subject and an optional wrapped body, then commits with a co-author attribution.

How do I verify that my git commit included the correct files and changes?▼

To verify your git commit included the correct files and changes, the skill performs a final commit stat verification. This step confirms the committed changes match your explicitly staged file selection and expected diff output.