commit

Create conventional git commits with structured messages and Co-Authored-By metadata.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clean, well-structured git commits, reducing manual drift and ensuring consistent history across a project.

Core Features & Use Cases

  • Automatic commit structuring: Groups related changes into logical commits according to type (feat, fix, docs, chore, refactor).
  • Message guidelines: Enforces conventional-style messages and supports multi-line bodies with optional Co-Authored-By metadata.
  • Use Case: When reviewing changes, generate precise commit messages and push a clean history that aligns with team conventions.

Quick Start

Use the /commit command to generate commits for staged changes or describe the changes you want to commit to create structured messages.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automatically generate conventional commit messages for staged git changes?

You can automatically generate conventional commit messages by applying this Skill to your staged git changes. It groups related modifications into logical commits and enforces standard types like feat, fix, and docs.

Can I group related code changes into a single structured git commit automatically?

Yes, you can group related code changes automatically. The Skill reviews your modifications and organizes them into logical, well-structured commits based on their type and scope.

Does this tool support multi-line commit bodies with Co-Authored-By metadata?

The tool supports multi-line commit bodies with Co-Authored-By metadata. It enforces conventional-style messaging guidelines to maintain a clean and consistent project history.

What is the best way to ensure my git commits follow conventional commit standards?

The best way to ensure conventional commit standards is to use this automation Skill during your review and staging process. It structures messages automatically according to type, features, and fixes.

How do I commit features, fixes, and docs with proper conventional types?

To commit features, fixes, and docs with proper types, use the /commit command on your staged changes. The Skill categorizes modifications and applies the correct conventional prefix.

Do I need any specific dependencies to automate my version control commits?

No specific dependencies are required to automate your version control commits. The Skill operates independently to review changes, stage modifications, and push a clean history.