commit

Create structured git commits for staged changes with standard message types.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/gaodes/marvin --skill commit-gaodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gaodes/marvin/tree/main/skills/commit
Command: npx skills add https://github.com/gaodes/marvin --skill commit-gaodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure every git commit is meaningful, well-structured, and easy to review by guiding users to group changes, choose appropriate message types, and maintain consistency across the repository.

Core Features & Use Cases

  • Logical grouping of changes into commits by type (feat, fix, docs, chore)
  • Enforce descriptive commit messages and optional body
  • Improve code review and change history across collaborations

Quick Start

Tell me to create clean, structured commits for the current changes with meaningful messages.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate structured git commit messages for staged changes?▼

Automating structured git commit messages involves grouping staged changes by type, such as feat or fix, and generating a descriptive subject with an optional body to maintain repository consistency.

What is the best way to group code changes into logical git commits?▼

The best way to group code changes into logical git commits is to categorize modifications by standard vocabularies like feat, fix, docs, and refactor, ensuring each commit represents a single meaningful update.

How do I enforce consistent commit messages across a development team?▼

To enforce consistent commit messages across a development team, apply a standard commit vocabulary and require a descriptive subject and optional body for every staged change to improve code review history.

Does this commit workflow support standard commit vocabularies like feat, fix, and chore?▼

Yes, this commit workflow supports standard commit vocabularies including feat, fix, docs, chore, and refactor to classify staged changes and enforce descriptive commit messages for team collaboration.

When do I need to use a standard commit format for version control?▼

You need to use a standard commit format for version control when your team requires consistent commit messages, logical grouping of changes, and an easily reviewable change history across feature updates and fixes.