commit

Stage git changes and generate conventional commit messages with confirmation.

Updated Apr 24, 2026

Search Tags:#automation #git #workflow #commit #staging #conventional-commit

Ready to run

npx skills add https://github.com/Utchash007/TermTales --skill commit-utchash007

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Utchash007/TermTales/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/Utchash007/TermTales --skill commit-utchash007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers stage the right files, draft a conventional commit message, and execute it with confirmation to maintain clean, consistent git history.

Core Features & Use Cases

Stages changes by inspecting git status and git diff --stat to prepare a clean commit candidate.
Drafts conventional commit messages with type, optional scope, and a descriptive message based on the staged diffs and user input.
Executes the commit only after explicit user confirmation, preserving branch context and history integrity.
Supports workflows across ad-hoc changes, planning steps, and iterative development.

Quick Start

Provide an optional message hint (e.g., '/commit fix login bug') to tailor the draft.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I stage changes and generate a conventional commit message automatically?▼

To stage changes and generate a conventional commit message, inspect git status and git diff --stat to identify a clean set of changes, then draft a message with a type, optional scope, and description based on the staged diffs and an optional hint.

What is the best way to ensure my git commit history follows conventional commit standards?▼

The best way to ensure your git commit history follows conventional commit standards is to draft commit messages with a specific type, optional scope, and description derived directly from your staged diffs, executing the commit only after explicit confirmation.

Can I provide a custom hint to tailor my conventional commit message draft?▼

Yes, you can provide an optional message hint to tailor your conventional commit message draft, which supplements the staged diffs to generate a more specific type, scope, and description for your commit.

How does staging files with git diff --stat work before a conventional commit?▼

Staging files with git diff --stat works by inspecting the statistics of changed files to prepare a clean set of changes for your commit candidate, ensuring only the intended modifications are included before drafting the conventional commit message.

Does the automated commit process execute immediately or require user confirmation?▼

The automated commit process requires explicit user confirmation before executing, which preserves branch context and history integrity by ensuring you review the staged changes and drafted conventional commit message beforehand.

When should I not use an automated staging and conventional commit workflow?▼

You should not use an automated staging and conventional commit workflow when you need to amend previous commits or manage complex merge conflicts, as this process focuses on identifying clean change candidates and drafting new conventional commit messages.