git-commit

Generate conventional commit messages from git working tree changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/junnv93/equipment_management_system --skill git-commit-junnv93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/junnv93/equipment_management_system/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/junnv93/equipment_management_system --skill git-commit-junnv93

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces manual overhead by translating a set of git changes into a conventional commit message and selecting an appropriate push workflow.

Core Features & Use Cases

  • Generate a standards-compliant conventional commit message from staged and/or unstaged changes.
  • Auto-select the workflow based on change size (direct push to main for small changes, branch+PR for larger changes).
  • Respect user directives to create a PR or push directly, and provide guidance for follow-up steps.

Quick Start

Describe your git changes and I will generate a conventional commit message and select the proper workflow.

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 git changes?

To generate a conventional commit message, describe your staged or unstaged git changes. The skill evaluates the working tree and automatically produces a standards-compliant commit message based on those changes.

How does git workflow automation decide between a direct push and a pull request?

Git workflow automation selects the workflow by evaluating change size. It directs small changes to a push on main, while larger changes trigger a branch creation and pull request workflow.

Can I force a pull request creation for small conventional commits?

Yes, you can force pull request creation. The workflow respects user directives for PR creation or direct pushes, overriding the default change size evaluation logic.

What is the best way to automate version control commits for large changes?

Automating version control commits for large changes is handled by creating a branch and pull request. The skill identifies the changes and selects the branch+PR workflow to ensure proper review.

Does the conventional commit generator provide guidance for follow-up steps?

Yes, the conventional commit generator provides guidance for follow-up steps. It respects user directives and advises on the appropriate actions after evaluating your git changes.