commit

Analyze staged changes and generate standardized git commit messages.

1.0k|178|Updated Jan 13, 2026

Search Tags:#automation #git #workflow #commit #code-review #version-control #message-guidance

Ready to run

npx skills add https://github.com/SterlingChin/marvin-template --skill commit-sterlingchin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SterlingChin/marvin-template/tree/main/skills/commit
Command: npx skills add https://github.com/SterlingChin/marvin-template --skill commit-sterlingchin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create clean, consistent git commits by guiding a structured workflow and automating best-practice messaging.

Core Features & Use Cases

Structured Commit Messages: Ensure commits follow conventional types and include meaningful descriptions.
Change Granularity & Grouping: Segment changes into features, fixes, docs, and configuration for clear history.
Use Case: While working on a bug fix, you run /commit to generate a set of logical commits and push with style guidelines.

Quick Start

Run /commit to review and commit changes in your current repository. Follow prompts to categorize changes and craft messages. If needed, configure your git user.name and user.email.

Frequently Asked Questions about commit

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

FAQPage Schema

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

You can automate git commit messages by running /commit to analyze staged changes and propose standardized messages. This workflow categorizes changes into features, fixes, docs, and configurations to ensure clear history.

What is conventional commit message formatting for feature and fix types?▼

Conventional commit message formatting uses standardized types like feat, fix, docs, and chore to categorize changes. This structure ensures commits follow conventional types and include meaningful descriptions for clear version control history.

How do I group staged code changes into logical commits?▼

To group staged code changes into logical commits, the /commit workflow segments changes by granularity. It categorizes changes into features, fixes, docs, and configuration to maintain a well-structured and clear git history.

Can I add Co-Authored-By formatting to my git commits?▼

Yes, you can apply optional Co-Authored-By formatting to your git commits. The commit workflow supports optional Co-Authored-By formatting to attribute changes appropriately within your version control practices.

Do I need to configure git user.name and user.email before committing?▼

You need to configure your git user.name and user.email before committing if they are not already set. This prerequisite ensures your version control changes are correctly attributed to you during the commit workflow.