git-commit

Analyze code diffs to stage files and generate Conventional Commits messages.

6|8|Updated Apr 22, 2023
One-click install
npx skills add https://github.com/Ansteorra/KMP --skill git-commit-ansteorra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Ansteorra/KMP/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/Ansteorra/KMP --skill git-commit-ansteorra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Git commits by automating the analysis of code changes and generating well-formatted, conventional commit messages.

Core Features & Use Cases

  • Conventional Commits: Enforces the Conventional Commits specification for standardized commit messages.
  • Intelligent Staging: Helps in staging relevant files for a commit.
  • Message Generation: Analyzes code diffs to suggest appropriate commit types, scopes, and descriptions.
  • Use Case: When you've finished a feature, use this Skill to automatically determine the commit type (feat), scope (e.g., auth), and a concise description based on your code changes, ensuring consistency across the project.

Quick Start

Use the git-commit skill to create a commit with an automatically generated conventional commit 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 automatically from code diffs?

To generate conventional commit messages, this Skill analyzes your Git code diffs to intelligently stage files and suggest the commit type, scope, and description. It automates the entire process while enforcing the Conventional Commits specification for project consistency.

Can I override the automatically generated Git commit type and scope?

Yes, you can override the automatically generated Git commit details. The Skill supports interactive overrides, allowing you to manually adjust the commit type, scope, and description to ensure the message accurately reflects your code changes before finalizing.

What is the Conventional Commits specification and why use it for version control?

The Conventional Commits specification is a standardized format for Git commit messages that includes a type, scope, and description. Using it for version control ensures commit hygiene, makes project history readable, and automates semantic versioning and changelog generation.

How do I stage relevant files for a Git commit without manual selection?

You can stage relevant files automatically by letting the Skill analyze your code changes. It performs intelligent staging to determine which modified files belong together, streamlining the Git commit process and preventing unrelated changes from being included in the same commit.

Does this Git commit tool enforce commit hygiene and safety protocols?

Yes, the Git commit tool enforces commit hygiene and safety protocols. By adhering to the Conventional Commits specification and intelligently analyzing code diffs, it ensures standardized, safe, and consistent commit messages across your version control history.

What's the best way to structure a commit message for a new feature?

The best way to structure a commit message for a new feature is using the Conventional Commits format. This Skill automatically determines the `feat` type, identifies the scope like `auth`, and writes a concise description based on your specific code changes.