commit

Create conventional commits with automatic git state integration.

16|3|Updated May 5, 2026
One-click install
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill commit-kevin-liu-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/commit
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill commit-kevin-liu-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating conventional commits manually is error-prone and inconsistent; this Skill standardizes commit messages and captures current git state for traceability.

Core Features & Use Cases

  • Enforces the conventional commit format (type(scope): description) for all commits.
  • Automatically captures git status, branch, and recent commits to inform commit content.
  • Supports staging changes by file to create atomic, meaningful commits.

Quick Start

Stage changes and commit using the conventional format with the current git state.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits automatically using my current git state?

To create conventional commits automatically, this Skill captures your current git status, branch, and recent commits to standardize messages in the type(scope): description format. It validates the commit shape against allowed types and scope constraints for consistent history.

What's the best way to enforce conventional commit format across features, fixes, refactors, and docs?

Enforcing the conventional commit format across features and fixes requires standardizing message structure. This Skill validates the commit shape against allowed types and scope constraints, ensuring consistent version-control history without manual formatting errors.

Do I need external tooling to automate conventional commits with git?

No external tooling is required to automate conventional commits beyond Git itself. This Skill operates independently to capture git state and validate commit messages, requiring no additional dependencies or external installation to standardize your workflow.

Can I stage changes by file to create atomic conventional commits?

Yes, you can stage changes by file to create atomic, meaningful conventional commits. This Skill supports selective file staging to ensure that each commit captures a logical, isolated unit of work for better project traceability.

Why does my git history have inconsistent conventional commit messages?

Inconsistent conventional commit messages occur when creating commits manually. This Skill solves the problem by automatically capturing git state and enforcing the type(scope): description format, eliminating human error and standardizing version-control history.

When do I need to use conventional commit format in my version-control workflow?

You need the conventional commit format in version-control when maintaining consistent project history across features, fixes, refactors, and docs. This Skill applies standard formatting to capture current git state for traceability and automated state integration.