mp-commit

Stage and commit Git changes with conventional commit messages.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MartinoPolo/mxp-claude-code --skill mp-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-commit
Source: https://github.com/MartinoPolo/mxp-claude-code/tree/main/skills/mp-commit
Command: npx skills add https://github.com/MartinoPolo/mxp-claude-code --skill mp-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages and standardizes code changes by enforcing conventional commit messages to improve traceability and collaboration.

Core Features & Use Cases

  • Conventional commits: enforce a consistent commit message structure (type(scope): description).
  • Selective staging: stage only the files you want to include, reducing the risk of committing unintended changes.
  • Audit trail: after commit, output hash, message, and files changed summary for traceability.

Quick Start

Stage changes and commit them using a conventional commit message.

Frequently Asked Questions about mp-commit

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

FAQPage Schema
How do I stage and commit changes using conventional commits?

To stage and commit changes with conventional commits, you selectively stage files and generate a structured message following the type(scope): description format, which outputs the commit hash, message, and changed files summary.

What are conventional commits and when do I need them for version control?

Conventional commits are a standardized message structure using type(scope): description format. You need them in Git-based repositories to enforce consistent history, improve traceability for features, fixes, and chores, and enhance collaboration.

Can I selectively stage files before creating a conventional commit?

Yes, you can selectively stage only the files you want to include in a conventional commit. This selective staging reduces the risk of committing unintended changes by ensuring only specified modifications are committed.

Do I need a clean working tree to create conventional commits?

Yes, you need a clean working tree to create conventional commits. The commit process requires a clean working tree to ensure file selection guidelines are respected and standardized messages are applied accurately.

How do I get an audit trail after committing changes to a Git repository?

To get an audit trail after committing changes, the process outputs a summary containing the commit hash, commit message, and a list of changed files. This provides traceability for features, fixes, and chores in your repository.