commit

Group staged changes into conventional git commits by type.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/m43nu/MARVIN --skill commit-m43nu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/m43nu/MARVIN/tree/main/skills/commit
Command: npx skills add https://github.com/m43nu/MARVIN --skill commit-m43nu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changes and create clean, well-structured git commits. Use when you type /commit or ask to commit changes. This Skill helps you produce well-organized commit messages that reflect changes accurately.

Core Features & Use Cases

  • Review current changes with git status and git diff to understand what was modified.
  • Group related changes into logical commits by type (feat:, fix:, docs:, chore:, refactor:, test:).
  • Generate, stage, and apply commits with consistent messaging that matches project conventions.

Quick Start

Tell me to commit my changes and the skill will generate structured commits following conventional patterns.

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 automatically from staged changes?

To generate conventional commit messages, this Skill reviews your staged changes with git diff and groups them by type, such as feat: or fix:, to produce well-structured git commits that match project conventions.

What is the best way to group related git changes into logical commits by category?

Grouping related git changes involves reviewing git status and git diff, then categorizing modifications into conventional types like docs:, chore:, or refactor: to maintain a clean version-control history.

Can I use this to automate staging and applying commits for software development workflows?

Yes, you can automate staging and applying commits for software development workflows by instructing the Skill to commit changes, which generates consistent messaging and stages related modifications.

Does this Skill support all conventional commit types like feat, fix, and test?

This Skill supports conventional commit types including feat:, fix:, docs:, chore:, refactor:, and test:, ensuring your version-control messages accurately reflect the software development changes made.

Why should I structure my git commit messages following conventional patterns?

Structuring git commit messages following conventional patterns ensures changes are accurately reflected and grouped by type, which maintains a clean, readable version-control history for software development automation.