creating-commit

Automate git commit workflows with validation gates and user approval.

5|4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/cblecker/claude-plugins --skill creating-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-commit
Source: https://github.com/cblecker/claude-plugins/tree/main/plugins/git-workflows/skills/creating-commit
Command: npx skills add https://github.com/cblecker/claude-plugins --skill creating-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating atomic, well-structured git commits with clear, conventional messages. It guides you through staging changes, analyzes your modifications, and helps generate a concise commit message, ensuring a clean and meaningful commit history without manual effort.

Core Features & Use Cases

  • Pre-flight Checks: Verifies branch protection and working tree status to prevent accidental commits on mainline.
  • Change Analysis: Categorizes file changes and detects conventional commit usage to inform message generation.
  • Automated Message Generation: Drafts a concise and informative commit message, adhering to Conventional Commits standards if detected.
  • Use Case: When you're ready to save your work, simply say "commit these changes," and the Skill will help you stage files, generate a professional commit message, and finalize the commit, keeping your project history pristine.

Quick Start

Commit my staged changes with a message describing the new feature.

Frequently Asked Questions about creating-commit

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

FAQPage Schema
How do I write better git commit messages automatically?

Automated commit message generation analyzes your staged changes and drafts conventional commit messages that follow standard formatting, ensuring consistent, meaningful commit history without manual composition effort.

Can I prevent accidental commits to main branches?

Branch protection checks verify your working tree status and branch context before committing, blocking unsafe commits to mainline branches and protecting your primary codebase from unwanted changes.

How do I implement conventional commits in my workflow?

Conventional commit automation detects your project's commit format, categorizes file changes, and generates standardized messages with type and scope prefixes, maintaining compliance across your repository history.

What's the best way to stage and commit changes consistently?

A four-phase commit process gathers context from your modifications, generates a descriptive message, obtains your approval before execution, and validates the commit with pre-commit handling and branch checks.

Can I add co-authored-by credits to commits automatically?

Optional co-authored-by support embeds collaborator attribution directly into commit metadata during the automated commit process, preserving contribution records within your version control history.

Why should I use structured commits for feature branches?

Atomic, well-structured commits with clear messages keep feature-branch history clean and reviewable, reducing merge conflicts and making your project's development timeline easier to audit and bisect.