commit

Generate Git commits following the Conventional Commits specification.

437|40|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/HazAT/pi-config --skill commit-hazat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/HazAT/pi-config/tree/main/skills/commit
Command: npx skills add https://github.com/HazAT/pi-config --skill commit-hazat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all Git commits adhere to the Conventional Commits standard, producing clear, descriptive, and consistent commit messages that improve code history readability and automation.

Core Features & Use Cases

  • Conventional Commits: Automatically formats commit messages with type, scope, and a concise summary.
  • Detailed Body: Encourages and helps generate a descriptive body explaining the 'what' and 'why' of a change.
  • Use Case: When you've finished a bug fix, use this skill to generate a commit message like fix(api): resolve user authentication issue with a detailed explanation of the fix.

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 write conventional commits for my git history?

Conventional commits require a structured format including type, optional scope, and a descriptive summary. This skill generates git commits following the conventional commits specification to improve code history readability and automation consistency.

Why should I include a detailed body in my conventional commit messages?

A detailed body in conventional commit messages explains the rationale and implementation of changes. This skill encourages generating a descriptive body explaining the 'what' and 'why' of your change, improving overall code history readability for future reference.

Can I generate a git commit message for specific file path changes?

Yes, you can generate a git commit message for specific file path changes. This skill supports user-provided instructions and file path limitations, allowing you to create targeted commits that only include and describe your specified code modifications.

What is the best way to format a bug fix commit message in version control?

The best way to format a bug fix commit message is using a structured type like `fix` with a scope and summary. This skill creates messages like `fix(api): resolve user authentication issue` paired with a detailed explanation of the fix.

Does this conventional commits generator work without external dependencies?

Yes, this conventional commits generator works without external dependencies. It functions as a standalone skill to format your version control history, requiring no additional components or libraries to structure your git commit messages.