git-commit

Generate Conventional Commits messages by analyzing code diffs and staging files.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/xurenlu/marstaff --skill git-commit-xurenlu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/xurenlu/marstaff/tree/main/skills/git-commit
Command: npx skills add https://github.com/xurenlu/marstaff --skill git-commit-xurenlu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of standardized, semantic Git commits, ensuring consistency and clarity in your project's version history.

Core Features & Use Cases

  • Conventional Commits: Adheres to the Conventional Commits specification for structured commit messages.
  • Automated Analysis: Analyzes code diffs to intelligently determine commit type, scope, and description.
  • Interactive Commit: Allows for interactive overrides of type, scope, and message for fine-grained control.
  • Intelligent Staging: Helps stage files logically before committing.
  • Use Case: When you've finished a new feature, use this Skill to generate a feat: commit with an appropriate scope and description, ensuring your commit history is clean and informative.

Quick Start

Use the git-commit skill to commit your staged changes with an automatically generated conventional commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from git diffs?

You can automatically generate conventional commit messages by analyzing code diffs and staging files. The tool intelligently detects the commit type and scope from your changes, then constructs a structured message adhering to the Conventional Commits specification.

What is the best way to ensure my git commits follow semantic versioning standards?

Using conventional commits is the best way to ensure semantic versioning standards. This approach enforces structured commit messages with specific types and scopes, keeping your project's version history consistent, standardized, and informative.

How to stage files and create a conventional commit interactively?

You can stage files logically and create a commit interactively by overriding the automatically detected type, scope, and description. This allows fine-grained control over the final commit message while still adhering to the Conventional Commits specification.

Can I override the automatically detected commit type and scope when committing code?

Yes, you can override the automatically detected commit type and scope. The skill supports interactive commit message construction, allowing you to manually adjust the type, scope, and description for fine-grained control over your version history.

What safety protocols are enforced during automated git commit creation?

Strict Git safety protocols are enforced during automated commit creation to prevent destructive actions and unauthorized configuration changes. This ensures that your repository remains protected while the tool analyzes diffs and stages files.