commit

Draft final-state git commit messages with enforced style rules.

1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/MihaiOnSoftware/.ai --skill commit-mihaionsoftware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/MihaiOnSoftware/.ai/tree/main/skills/commit
Command: npx skills add https://github.com/MihaiOnSoftware/.ai --skill commit-mihaionsoftware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create precise, actionable commit messages that reflect final changes, reducing ambiguity and rework.

Core Features & Use Cases

  • Generate final-state messages: Describe only what changed to improve traceability.
  • Enforce style rules: Ensure active voice, conciseness, and alignment with the project’s commit standards.
  • Workflow integration: Works with existing git workflows by guiding staging, message drafting, and final commit creation.

Quick Start

Use this skill to generate a proper commit message for your current changes.

  • Check status with git status
  • Stage changes with git add -A
  • Generate the commit message with the skill and copy it into git commit -m "<message>"
  • Optionally add a body with extra context if needed

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a git commit message that follows strict writing style rules?

To generate a git commit message with strict writing style rules, draft a final-state message describing only the changes made, enforce active voice and conciseness, and reference project-specific commit guidelines for compliance.

What is a final-state commit message and when should I use it?

A final-state commit message describes only what changed in the working directory to improve traceability. Use this approach when you need precise, actionable git commit summaries that reduce ambiguity and rework.

How do I ensure my version control commits use active voice and concise language?

Ensure version control commits use active voice and concise language by applying automated commit message guidelines that enforce style rules, align with project standards, and draft messages reflecting only the final changes made.

What is the best way to integrate automated commit message drafting into my git workflow?

Integrate automated commit message drafting into your git workflow by checking git status, staging changes with git add, generating the compliant message, and executing git commit with the drafted message and optional body context.

Does this commit message generation approach work without pre-configured dependencies or components?

Yes, this commit message generation approach works without pre-configured dependencies or components, operating directly on your working directory changes to enforce active voice and project commit standards.