git-commit

Generate and create conventional git commits from staged changes.

42|8|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/sequenzia/claude-alchemy --skill git-commit-sequenzia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/sequenzia/claude-alchemy/tree/main/plugins/tools/skills/git-commit
Command: npx skills add https://github.com/sequenzia/claude-alchemy --skill git-commit-sequenzia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit changes by generating and applying a conventional commit message based on staged changes, ensuring consistency with project guidelines.

Core Features & Use Cases

  • Automatically stages all changes
  • Analyzes the diff to determine type, scope, and description
  • Constructs and creates a conventional commit
  • Reports the resulting commit hash or helps recover from pre-commit hook failures

Quick Start

Commit all staged changes with a conventional message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?

Yes, you can automate conventional commit creation by identifying staged changes and generating a formatted message that determines type, scope, and description directly from the diff analysis.

What is a conventional commit and how does diff analysis determine the type and scope?

A conventional commit standardizes version-control history. Diff analysis reviews staged changes to deduce the correct type, scope, and description, ensuring the commit message aligns with project guidelines.

How do I handle pre-commit hook failures when automating a git commit?

When pre-commit hooks fail during an automated commit, the system reports the failure details and provides remediation guidance, allowing you to resolve the blocking issues before attempting to commit again.

Can I automatically stage all changes before generating a conventional commit message?

Yes, the automation automatically stages all changes before analyzing the diff. It then generates the conventional commit message and returns the successful commit hash or reports any pre-commit hook failures.

Why does my automated conventional commit return a pre-commit hook failure instead of a commit hash?

Your automated commit returns a pre-commit hook failure instead of a commit hash when project validation scripts fail. It reports the failure with guidance for remediation so you can address the errors and retry.