commit

Generate conventional Git commit messages for staged changes.

16|2|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/maroffo/claude-forge --skill commit-maroffo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/maroffo/claude-forge/tree/main/skills/commit
Command: npx skills add https://github.com/maroffo/claude-forge --skill commit-maroffo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Git commits by enforcing the conventional commit format, ensuring consistency and clarity in your project's commit history.

Core Features & Use Cases

  • Conventional Commits: Automatically formats your commit messages according to established conventions (e.g., feat:, fix:, chore:).
  • Staged Changes: Designed specifically for committing changes that have already been staged using git add.
  • Use Case: After making several code changes, you can invoke this skill to generate a commit message like feat: Add user authentication endpoint for new features, or fix: Resolve memory leak in data processing for bug fixes.

Quick Start

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

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits for staged Git changes?

To create conventional commits, you stage your code changes with git add and invoke the commit skill to automatically generate a formatted commit message like feat: or fix: for your staged changes.

What is the conventional commit format and why use it for Git version control?

The conventional commit format uses structured prefixes like feat: and chore: to categorize code changes. Using it for Git version control ensures commit history consistency and aids in automated changelog generation.

Can I use this commit skill for complex Git operations like branch management?

No, this skill is designed specifically for routine code commits of staged changes. It does not handle complex Git operations like branch management or rebasing, focusing only on generating conventional commit messages.

How do I automatically generate a commit message for a new feature?

To automatically generate a commit message for a new feature, stage your code and invoke the skill. It analyzes the changes and outputs a conventional message such as feat: Add user authentication endpoint.

What are the limitations of automating Git commit messages with this skill?

The main limitation is that it only processes changes that are already staged using git add. It is restricted to routine code commits and will not perform complex Git operations like branch management or rebasing.