commit

Automate a gated git commit workflow with conventional messages and pre-commit checks.

26|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Llloooggg/LetsFLUTssh --skill commit-llloooggg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Llloooggg/LetsFLUTssh/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Llloooggg/LetsFLUTssh --skill commit-llloooggg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a disciplined git commit process that adheres to project conventions and runs pre-commit checks, ensuring commits are consistent and safe.

Core Features & Use Cases

  • Enforces standardized commit messages that align with project conventions and changelog practices.
  • Integrates pre-commit checks and documentation validation to catch issues before commits are recorded.
  • Defines a gated workflow: gather repository state, analyze changes, draft a conventional message, confirm with the user, and optionally push.

Quick Start

Prompt the AI to execute a gated commit workflow: gather state, analyze changes, draft a conventional message, confirm with the user, and perform commit with optional push.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commit messages in my git workflow?

Automating standardized commit messages involves a gated workflow that gathers repository state, analyzes changes, drafts a conventional message, and prompts user confirmation before committing. This ensures consistent history and safe changes.

What is a gated git commit workflow and when do I need it?

A gated git commit workflow is a disciplined process that gathers state, analyzes changes, drafts a conventional message, confirms with the user, and optionally pushes. You need it when enforcing project conventions and pre-commit checks for consistent versioning history.

How do I enforce pre-commit checks and standardized commit messages?

To enforce pre-commit checks and standardized commit messages, use a rules-driven automation workflow that integrates validation and documentation checks before committing. This catches issues early and aligns commit messaging with project changelog practices.

Can I automatically push git commits after drafting a conventional message?

Yes, you can optionally push git commits after the gated workflow completes. The process analyzes changes, drafts a conventional message, prompts for user confirmation, performs the commit, and then optionally executes a push to the remote repository.

Does automated version bumping work with standardized git commit messages?

Automated version bumping works with standardized git commit messages by requiring automated version bump hooks within the gated workflow. This ensures safe changes and consistent versioning history aligned with project conventions and changelog practices.

Why should I use an automated workflow for conventional commits instead of manual git commits?

Using an automated workflow for conventional commits enforces project conventions, integrates pre-commit checks, and standardizes messaging to catch issues before they are recorded. Manual commits often skip validation, leading to inconsistent history and unsafe changes.