commit

Create convention-compliant Git commits from staged or unstaged changes.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill commit-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/gittower/git-flow-next --skill commit-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a set of staged or unstaged Git changes into a properly formatted commit without guessing the project’s commit conventions.

Core Features & Use Cases

  • Commit Analysis: Reviews the current diff and status to understand what changed before writing the commit.
  • Convention-Aware Messaging: Reads COMMIT_GUIDELINES.md and selects the right commit type, scope, subject, body, and footer.
  • Git Workflow Execution: Creates the commit and verifies the final message so the result is consistent and review-ready.
  • Use Case: You’ve finished a small fix or refactor and want the repository’s preferred commit message written and applied correctly.

Quick Start

Use the commit skill to inspect my Git changes and create a commit message that follows the repository guidelines.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a convention-compliant Git commit message from my current changes?

To create a convention-compliant Git commit, this Skill analyzes your staged or unstaged repository diffs and formats the commit message according to your project's specific guidelines.

How does this workflow determine the correct commit type and scope for my repository?

It determines the commit type and scope by reading your repository's COMMIT_GUIDELINES.md file, analyzing the actual code diffs, and selecting the appropriate type, scope, subject, and body.

Can I use this to analyze unstaged Git changes without manually staging files first?

Yes, you can analyze unstaged Git changes. The workflow reviews both staged and unstaged repository status to understand what changed before generating and applying the final commit.

What is the best way to ensure my commit messages match project standards automatically?

The best way to ensure commit messages match project standards is to use a convention-aware tool that reads your commit guidelines, analyzes diffs, and verifies the final message before execution.

Does this process verify the final Git commit message before applying it to the repository?

Yes, the process verifies the final Git commit message. It creates the commit and checks the result to ensure the message is consistent, convention-compliant, and ready for code review.