git-commit

Generate conventional git commit messages and stage related file changes.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill git-commit-ian-pascoe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/git-commit
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill git-commit-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from committing changes by helping you inspect diffs, choose the right commit type, and write a clear conventional commit message.

Core Features & Use Cases

  • Diff Analysis: Reviews staged or unstaged changes to infer the most accurate commit type, scope, and description.
  • Intelligent Staging: Helps group related files logically so each commit stays focused and meaningful.
  • Safety Guardrails: Avoids secret files and discourages destructive git actions while keeping the workflow safe.
  • Use Case: After finishing a bug fix or feature update, use this Skill to stage the right files and produce a concise, standards-compliant commit message.

Quick Start

Ask the git-commit skill to review the current repository changes, stage the appropriate files, and create a conventional commit message for me.

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 staged git changes?

You can generate conventional commit messages by inspecting git diffs to infer the correct commit type, scope, and description, then staging the appropriate files to create a focused, standards-compliant commit.

What is the best way to group related file changes for a single git commit?

Intelligent staging analyzes working tree changes and groups related files logically, ensuring each git commit remains focused and meaningful rather than mixing unrelated modifications into a single commit.

Can I use this to review unstaged changes before committing to my local repository?

Yes, the diff analysis process reviews both staged and unstaged working tree changes, allowing you to inspect modifications and produce a concise conventional commit message before finalizing the commit.

How does conventional commit analysis determine the correct commit type and scope?

Conventional commit analysis inspects your code diffs to automatically infer the most accurate commit type, scope, and description based on the actual file modifications and logical changes detected.

Will committing secrets or sensitive files accidentally be prevented during git staging?

Safety guardrails automatically detect and avoid secret files during the staging process, while also discouraging destructive git operations to keep your local repository workflow secure.