commit

Stage files and generate type-scope-summary Git commit messages.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill commit-mj-agentlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-git/skills/mj-git-commit
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill commit-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your Git commits adhere to project standards, preventing rework and maintaining a clean, understandable commit history.

Core Features & Use Cases

  • Automated Staging: Guides you through staging files safely, excluding sensitive or large files.
  • Commit Message Generation: Enforces the <type>(<scope>): <summary> format, deriving scope from file paths.
  • Discipline Enforcement: Validates commit types against branch types to prevent common errors.
  • Split Detection: Identifies when large or mixed changes should be split into multiple logical commits.
  • Use Case: When you've made several changes to different parts of a project, this Skill helps you create distinct, well-described commits for each logical change, ensuring clarity before pushing.

Quick Start

Use the commit skill to stage all modified files and create a commit with the message 'feat(aec): add new email collection feature'.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write standardized Git commit messages for my project?

The Skill derives the scope from file paths and enforces a <type>(<scope>): <summary> format for Git commit messages, ensuring clean, standardized project history without manual formatting effort.

How do I split complex Git changes into multiple logical commits?

Split detection identifies large or mixed changes and suggests dividing them into multiple logical commits, ensuring each Git commit represents a distinct, clearly described project change.

How to exclude sensitive data and large files when staging Git commits?

Automated staging guides you through safely selecting files while excluding sensitive data and large files, preventing accidental commits of restricted information into your version control history.

Can I validate commit types against branch types to prevent Git workflow errors?

Discipline enforcement validates commit types against branch types during pre-commit validation, preventing common Git workflow errors and ensuring commits adhere to project standards before integration.

What is the best way to automate the Git commit process for code review?

Automating the Git workflow involves staging files, generating type-scope-summary messages, and enforcing branch discipline to produce review-ready, logically separated version control changes.