commit

Name: commit
Availability: InStock
Author: Digication

Generate conventional commit messages from changed files and diffs.

Updated Mar 24, 2026

Search Tags:#automation #git #commit #branching #conventional-commits #scope-inference

Ready to run

npx skills add https://github.com/Digication/claude-blueprint --skill commit-digication

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Digication/claude-blueprint/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Digication/claude-blueprint --skill commit-digication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional Git workflows struggle with consistent commit messages and branch hygiene. This Skill automates generating Conventional Commits from changes and coordinates optional branch creation, reducing drift and manual effort.

Core Features & Use Cases

Automatically derive a Conventional Commit message from staged changes and user input
Infer scope from changed files or omit it for root-level changes; optionally propose a branch name
Enforce conventional-commits rules, validate syntax, and provide an approval gate before applying changes

Quick Start

Provide a single, plain-language instruction to generate a commit and manage branching

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automatically generate conventional commit messages from git diffs?▼

Automatically generate conventional commit messages by analyzing changed files, diffs, and user intent. The tool infers an appropriate scope from changed paths or omits it for root-level changes, then requires your approval before staging and applying the commit.

What is the best way to enforce conventional-commits syntax and length constraints in git?▼

Enforce conventional-commits syntax and length constraints by validating generated messages against established rules before application. This automation ensures commit message consistency and reduces manual formatting effort across your branching workflow.

Can I automatically propose a branch name based on my staged changes?▼

Yes, you can automatically propose a branch name based on your staged changes. The tool identifies changed files and user intent to coordinate optional branch creation, requiring your approval before creating any new branch.

How do I infer a commit scope from changed file paths?▼

Infer a commit scope by analyzing the directory paths of changed files. The tool automatically derives an appropriate scope from changed paths or omits it entirely for root-level changes to maintain conventional commit compliance.

Do I need to manually stage files before generating a conventional commit?▼

No, you do not need to manually stage files beforehand. The tool identifies changed files and requires your approval before staging, applying the commit, and creating any new branch, streamlining the entire git workflow.