Stage git changes and generate conventional commit messages with confirmation.
npx skills add https://github.com/Utchash007/TermTales --skill commit-utchash007
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
This Skill helps developers stage the right files, draft a conventional commit message, and execute it with confirmation to maintain clean, consistent git history.
Provide an optional message hint (e.g., '/commit fix login bug') to tailor the draft.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
BSteffaniakGenerate Git commit messages from staged changes and write them for commit tools.
AndrewDrygaCreate semantic version tags from changelogs and push them to Git.
proven-xyzGenerate standardized git commit messages from diffs using Conventional Commits rules.
storm-softwareGenerate conventional commit messages for staged Git changes.
