Generate and apply Conventional Commits messages from git diffs.
npx skills add https://github.com/dhnt/dhnt --skill commit-dhnt
Please help me install this Agent Skill. Skill: commit Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/commit/commit Command: npx skills add https://github.com/dhnt/dhnt --skill commit-dhnt
This Skill turns messy diffs into a clear Conventional Commits message that explains the change’s intent, reducing guesswork during reviews and changelog generation.
Use Case: You changed a handful of files while fixing a regression—this Skill helps you write a proper fix: message (with a short why) and then performs the git commit.
Ask the AI to commit your current working changes with a Conventional Commits message that reflects the smallest correct scope and explains why the change was made.
High-intent search queries and answers about installing and using this skill.
To generate a conventional commit message from a git diff, the working tree changes are surveyed to draft an imperative subject under 72 characters and an optional why-focused body. This process scopes the changes accurately and stages only relevant files before applying the commit.
Writing a conventional commit message for mixed staged and unstaged changes requires surveying both states to determine the smallest honest scope prefix. The system identifies relevant files, stages them by name, and applies a formatted commit without bypassing hooks or rewriting history.
Automated diff review selects the correct conventional commit scope by inspecting file changes and grouping them into the smallest accurate category like feat, fix, or refactor. It ensures the commit subject clearly explains the change intent for review and changelog readiness.
Yes, you can automate git commit message generation safely without bypassing hooks or rewriting history. The system stages files by name and commits using a heredoc, then verifies the repository status to ensure workflow-friendly and authorized changes.
A conventional commit subject should be limited to 72 characters to ensure readability across git interfaces and changelogs. This constraint forces a concise, imperative summary of the diff, reducing guesswork during code reviews.
You need to include a body paragraph in a conventional commit message when the diff requires explaining the motivation behind the change. This optional body focuses on the why, providing context that the code changes alone cannot convey for future review.
sommioGenerate conventional git commit messages from the working tree and commit changes.
allanninalConvert git commits into changelogs following Keep a Changelog and Conventional Commits.
malwareboEnforce code hygiene checks on staged Git files with ESLint and stylelint.
joegoldinStage, unstage, and inspect Git hunks by hash non-interactively.
