commit

Stage changes and commit with standardized 15-20 word messages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/flesler/dotfiles --skill commit-flesler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/flesler/dotfiles/tree/main/home/.cursor/skills/commit
Command: npx skills add https://github.com/flesler/dotfiles --skill commit-flesler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit current work with standardized message format to improve clarity and traceability of changes across projects.

Core Features & Use Cases

  • Enforces an action-verb plus a concise description within 15-20 words for every commit
  • Guides staging by prompting to add changes when needed and ensures explicit user confirmation before committing
  • Provides examples like "Implement the new invoice matching logic" to illustrate proper messages

Quick Start

Ask me to commit changes and I will stage eligible changes, then craft a concise 15-20 word message and perform the commit

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce a standardized git commit message format for my repository?

To enforce standardized commit messages, this process requires you to provide an action-verb plus a concise description within 15-20 words. It applies to software development workflows requiring consistent history and clear change descriptions across repositories.

Can I automatically stage and commit all my git changes at once?

Automatic staging and committing is avoided by this approach, which requires explicit prompts to commit. It guides staging by prompting you to add changes when needed and ensures explicit user confirmation before performing any version-control commit.

What is the required length and structure for a standardized commit message?

A standardized commit message requires an action-verb plus a concise description within 15-20 words. Examples include "Implement the new invoice matching logic" to illustrate proper formatting and maintain clear change descriptions across your project.

How do I stage changes and commit them with a consistent message format?

To stage changes and commit with a consistent message format, you explicitly request a commit, then eligible changes are staged and a 15-20 word action-verb message is crafted for your confirmation before the version-control commit is performed.

Does this commit workflow require manual confirmation before pushing changes?

Yes, the commit workflow requires manual prompts to commit and ensures explicit user confirmation before performing any commits. It avoids automatic staging, meaning you must explicitly request changes to be staged and committed in your repository.