Analyze working tree diffs and generate atomic git commit messages.
npx skills add https://github.com/thoughtbot/rails-consultant --skill git-commit-thoughtbot
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/thoughtbot/rails-consultant/tree/main/skills/git-commit Command: npx skills add https://github.com/thoughtbot/rails-consultant --skill git-commit-thoughtbot
This skill solves the problem of messy, poorly documented, or overly large git commits by enforcing an atomic, "why-focused" commit strategy that makes project history readable and maintainable.
Ask the assistant to commit the current changes with a note about the recent refactor to the user authentication flow.
High-intent search queries and answers about installing and using this skill.
Git commit messages are generated automatically by analyzing working tree diffs to produce context-rich explanations. The automation groups related changes logically and follows professional standards like imperative mood subject lines and detailed explanatory bodies.
Atomic git commits are created by analyzing your working tree diff and grouping related changes into logical, coherent commits. This prevents dumping all modifications at once and ensures project history remains clean and maintainable.
Co-author attribution is automated properly within the generated commit messages. The automation ensures consistent team communication by applying proper attribution alongside professional, context-rich documentation of the changes.
A clean git history for code review is maintained by enforcing an atomic, why-focused commit strategy. This approach makes project history readable by generating professional commit messages that explain the reasoning behind each change.
Automated commit generation works with software development workflows by analyzing diffs from complex features involving model changes, controller logic, and tests. It bundles the work into a single, clean commit with a descriptive message and proper attribution.
Automated git commit generation should be avoided when you need to dump all changes at once without logical grouping. It is designed for workflows requiring clean, maintainable version control history and consistent team communication through well-documented commits.
CivicActionsGroup unstaged changes into atomic git commits using project conventions.
j-cogburnEnforce atomic commits, branch naming, and pre-commit hygiene checks in git workflows.
julianobarbosaAutomate Git commits with pre-commit security scans and Conventional Commits enforcement.
RonnasaydGenerate structured Pull Request descriptions from git diffs and commit history.
