One-click install
npx skills add https://github.com/mfmezger/ai_agent_dotfiles --skill commit-mfmezger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mfmezger/ai_agent_dotfiles/tree/main/shared/skills/commit
Command: npx skills add https://github.com/mfmezger/ai_agent_dotfiles --skill commit-mfmezger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create clear, consistent, and informative Git commit messages, improving code history readability and maintainability.

Core Features & Use Cases

  • Conventional Commits: Enforces a standardized format for commit messages (<type>(<scope>): <summary>).
  • Automated Formatting: Guides the creation of subject lines, including type, scope, and a concise summary.
  • Use Case: After completing a bug fix, use this Skill to generate a commit message like fix(auth): resolve login redirect loop to clearly document the change.

Quick Start

Use the commit skill to create a git commit for the current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for Git changes?

To generate conventional commit messages for Git, this Skill analyzes your repository status and creates a structured format like `fix(auth): resolve login redirect loop` to ensure code history clarity.

What is the conventional commits format for structuring code history?

The conventional commits format structures code history by enforcing a standardized pattern of `<type>(<scope>): <summary>`, which documents the type of change, its scope, and a concise summary.

How do I write a Git commit message after fixing a bug?

To write a Git commit message after a bug fix, the Skill guides the creation of an automated subject line using the `fix` type, a relevant scope, and a concise summary of the resolved issue.

Do I need the Git CLI installed to use this commit message generator?

Yes, you need the Git CLI installed and available in your environment, as this Skill requires Git CLI to stage and commit files based on your current repository status.

Can this tool automatically stage files and create a Git commit?

Yes, this tool can automatically stage and create a Git commit by utilizing the Git CLI to process your current repository status and stage files based on your provided instructions.

Why should I use a standardized format for my Git commit messages?

Using a standardized format for Git commit messages improves code history readability and maintainability, ensuring that team members can quickly understand the context and scope of changes made.