git-commit

Generate Conventional Commits messages from repository diffs with staging recommendations.

9|1|Updated Jul 21, 2025
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill git-commit-usepowershell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/usepowershell/PoshMcp/tree/main/.squad/templates/skills/git-commit
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill git-commit-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the friction of crafting standardized, semantic git commit messages by analyzing repository diffs, intelligently staging related files, and producing Conventional Commits-compliant messages so developers can maintain clear history with minimal manual effort.

Core Features & Use Cases

  • Analyze staged and unstaged diffs to infer commit type (feat, fix, docs, etc.) and a meaningful scope.
  • Suggest and generate one-line conventional commit descriptions plus optional body and footers, with interactive overrides for type, scope, and message.
  • Provide intelligent file staging recommendations and enforce safety rules to avoid committing secrets or performing destructive git operations.
  • Use Case: When a developer finishes a small feature across several files, generate a single logical conventional commit that groups related changes, stages the appropriate files, and commits with a well-formed message.

Quick Start

Create a conventional commit for the current repository changes, auto-detect type and scope, stage logical files if needed, and commit with the generated semantic 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 git diffs?

To generate conventional commit messages from git diffs, this skill analyzes your staged and unstaged repository changes to infer the commit type and scope, then produces a Conventional Commits-compliant message automatically.

What is the best way to group related file changes into a single logical commit?

The best way to group related file changes into a single logical commit is using intelligent staging recommendations, which analyze repository diffs to stage appropriate files together based on their logical relationship.

Can I override the auto-detected commit type and scope for my staging area?

Yes, you can override the auto-detected commit type and scope. The skill provides interactive overrides for type, scope, and message, allowing you to manually adjust the generated conventional commit description before finalizing.

How does this approach prevent committing secrets or performing destructive git operations?

This approach prevents committing secrets and destructive git operations by enforcing built-in safety rules during diff analysis and file staging, ensuring sensitive data is excluded and your repository state remains protected.

Do I need to manually stage files before creating a conventional commit?

No, you do not need to manually stage files beforehand. The skill analyzes both staged and unstaged changes, providing intelligent file staging recommendations to group related changes automatically before committing.