commit

Draft conventional-commit messages for staged Git changes.

36|7|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Mosaic-agent/Mosaic-fund-agent --skill commit-mosaic-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Mosaic-agent/Mosaic-fund-agent/tree/main/.gravity/skills/commit
Command: npx skills add https://github.com/Mosaic-agent/Mosaic-fund-agent --skill commit-mosaic-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts and applies conventional-commit messages for changes in a Git repository, reducing drift and review time.

Core Features & Use Cases

  • Drafts a type-prefixed subject and grouped body based on git status, diff, and log
  • Stages files by explicit name and creates a single commit with no push or amend
  • Works with user prompts like /commit to influence the commit message

Quick Start

Run /commit to analyze changes and draft a conventional-commit message.

Frequently Asked Questions about commit

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

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

To generate conventional commit messages for staged git changes, this Skill analyzes git status, diff, and log to draft a type-prefixed subject and grouped body. It stages files by explicit name and creates a single commit with no push or amend.

What is the best way to enforce consistent git commit semantics?

The best way to enforce consistent git commit semantics is to automatically draft type-prefixed commit messages based on repository diffs. This approach reduces drift and review time by applying audit-friendly history conventions without pushing or amending.

Can I use a custom prompt to influence the generated conventional commit message?

Yes, you can use custom prompts like /commit to influence the commit message. The Skill processes your prompt alongside git status and diff data to draft the conventional-commit message that best reflects your staged changes.

Does the commit workflow include pushing code to the remote repository?

No, the commit workflow does not include pushing code to the remote repository. The Skill explicitly enforces no push or amend operations, ensuring it only creates a local commit after drafting the conventional-commit message.

How does analyzing git log improve commit message generation?

Analyzing git log improves commit message generation by providing historical context for drafting conventional commit messages. Combined with git status and diff, this ensures the new commit aligns with existing repository patterns and maintains an audit-friendly history.

What are the limitations of automating git staging and committing?

Limitations of automating git staging and committing include the inability to push to a remote or amend previous commits. The Skill also requires explicit file names for staging rather than automatically staging all modified files in the repository.