Stages pending changes and creates Conventional Commits messages from git diffs.
npx skills add https://github.com/rogerznts/anvil --skill tea-commit-rogerznts
Please help me install this Agent Skill. Skill: tea-commit Source: https://github.com/rogerznts/anvil/tree/main/anvil/.claude/skills/tea-commit Command: npx skills add https://github.com/rogerznts/anvil --skill tea-commit-rogerznts
git status and git diff to summarize changes and produce an accurate commit message instead of guessing from filenames. - Conventional Commits formatting: Generates type(scope): description messages using standard types like feat, fix, refactor, chore, docs, test, style, perf, and ci. - Debug code detection: Warns when console.log, var_dump, dd(), print_r, or debugger statements are present before committing. - Hook-safe commits: Never uses --no-verify; if a pre-commit hook fails, it reports the output and stops. - Use Case: After finishing a bug fix across several files, ask the assistant to commit your changes and receive a properly formatted fix(auth): correct token expiry check commit with hook validation intact. ## Quick Start Ask the assistant to review my pending changes and commit them with a Conventional Commits message.High-intent search queries and answers about installing and using this skill.
Run this Skill on your pending changes and it reads git status and git diff, summarizes the modifications, and proposes a message in the type(scope): description format. You review the message before it stages and commits.
The Skill runs git commit without the --no-verify flag, so all configured hooks execute normally. If a hook fails, it reports the failure output and stops instead of retrying or bypassing the check.
Yes, it scans the diff for common debug statements including console.log, var_dump, dd(), print_r, and debugger. When found, it warns you and asks whether to proceed or clean up first.
The Skill uses standard types: feat, fix, refactor, chore, docs, test, style, perf, and ci. Scope is optional but recommended, and descriptions use imperative mood, lowercase, and a 72-character limit.
If the working tree is clean, the Skill informs you and stops without attempting a commit. It always checks git status first to confirm pending changes exist.
Srajangpt1Apply code review fixes, run tests, and create a git commit.
santychuycomAnalyze diffs, create atomic conventional commits, push, and open pull requests.
owenlamontAutomate Python code linting and formatting with pre-commit hooks.
UtsavBalar1231Stage Git changes at file, hunk, or line-range granularity using the pgs CLI.