commit

Automate Git commits with git-cz style messages and optional push.

3|2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ukwhatn/.claude --skill commit-ukwhatn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/ukwhatn/.claude/tree/main/skills/commit
Command: npx skills add https://github.com/ukwhatn/.claude --skill commit-ukwhatn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the Git workflow by packaging the commit action into an easy command, reducing manual steps and ensuring consistent messaging.

Core Features & Use Cases

  • One-shot commit workflow: stage and commit changes with a single command, optionally pushing to the remote.
  • Consistent commit messages: guidance via git-cz style prompts to generate standardized messages.
  • Use Case: When you need quick, auditable commits across multiple files.

Quick Start

Invoke /commit to commit current changes and push automatically when --push is provided.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate a git commit and push in one step?

To automate a git commit and push in one step, you can invoke the command with the --push flag. This sequences status checks, staging, and git-cz style commit messaging, followed by an optional remote push, outputting the new commit hash.

What is the best way to generate standardized git commit messages automatically?

Generating standardized git commit messages automatically is handled using git-cz style prompts. This approach packages the commit action into an easy command, ensuring consistent messaging and reducing manual steps across multiple files.

Can I stage and commit changes across multiple files with a single command?

Yes, you can stage and commit changes across multiple files with a single command. The workflow sequences status checks and staging before committing, enabling quick, auditable commits without manual file selection.

Do I need any specific dependencies to use this git workflow automation?

No specific dependencies are required to use this git workflow automation. The skill operates independently to sequence status checks, staging, git-cz style messaging, and optional remote pushing without external components.

How does the automated commit process handle status checks and staging?

The automated commit process handles status checks and staging by sequencing them before the commit action. It evaluates the repository status, stages the identified changes, applies git-cz style messaging, and optionally pushes to the remote.

What are the limitations of using automated git commit workflows?

Limitations of using automated git commit workflows include relying on the built-in git-cz style messaging structure, which may lack context for highly complex changes. It is designed for quick, auditable commits rather than deeply customized version-control narratives.