create-git-commit

Generate Git commit messages from staged changes and historical commit analysis.

2|1|Updated Nov 16, 2018
One-click install
npx skills add https://github.com/softleader/slctl --skill create-git-commit-softleader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-git-commit
Source: https://github.com/softleader/slctl/tree/main/.agent/skills/create-git-commit
Command: npx skills add https://github.com/softleader/slctl --skill create-git-commit-softleader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Git commit messages, ensuring consistency and adherence to best practices, saving developers time and improving repository history clarity.

Core Features & Use Cases

  • Automated Message Generation: Creates commit messages based on repository style and past commit history.
  • Language and Style Detection: Automatically determines the language and commit style (Conventional Commits or simple).
  • Scope Identification: Extracts relevant scopes from commit history for use in messages.
  • Use Case: When you've finished a feature, use this Skill to generate a well-formatted commit message like feat(user): Add profile picture upload with a descriptive body, ensuring your team's Git log remains clean and informative.

Quick Start

Use the create-git-commit skill to generate a commit message for your staged changes.

Frequently Asked Questions about create-git-commit

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

FAQPage Schema
How do I generate a git commit message that matches my repository's history?

To generate a git commit message that matches your repository's history, this Skill analyzes your staged changes and past commit logs to determine the language, commit style, and relevant scopes for the output. It automatically detects whether to use Conventional Commits or a simple style based on your existing code history.

What is the best way to automate Conventional Commits formatting for staged changes?

The best way to automate Conventional Commits formatting is to use a tool that analyzes your staged changes and extracts relevant scopes from your commit history. This ensures consistent, well-formatted messages like `feat(user): Add profile picture upload` without manual formatting effort.

Can I automatically detect the correct commit scope from my version control history?

Yes, you can automatically detect the correct commit scope from your version control history. This Skill analyzes past commit logs to extract relevant scopes, ensuring newly generated commit messages align with your established project conventions and maintain clear code history.

Does this automated commit generation work with both simple and Conventional Commits styles?

Yes, this automated commit generation works with both simple and Conventional Commits styles. It analyzes your repository's historical commit logs to determine the existing commit style and language, then generates new messages that adhere to your detected software development workflow.

Why should I analyze past commit logs before writing a new git commit message?

You should analyze past commit logs before writing a new git commit message to ensure consistency and clarity in your repository history. Analyzing logs determines the appropriate language, commit style, and relevant scopes, which facilitates an informative and standardized version control record.