Create atomic Git commits using Conventional Commits conventions.
npx skills add https://github.com/dirien/yet-another-agent-harness --skill commit-dirien
Please help me install this Agent Skill. Skill: commit Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/commit Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill commit-dirien
Provides a disciplined, repeatable workflow for creating atomic, semantically meaningful Git commits so changes are easy to review, revert, and reason about.
Create an atomic Conventional Commit for the current staged changes, grouping related modifications and writing a concise subject with a descriptive body explaining why the change was made.
High-intent search queries and answers about installing and using this skill.
To create atomic git commits, you stage related modifications and generate a commit message using Conventional Commits conventions. This ensures each commit represents a single logical change, making modifications easy to review and revert.
The Conventional Commits format structures commit messages using specific prefixes like feat, fix, refactor, docs, test, and chore. This semantic structure categorizes the nature of changes for automated processing and clear version control history.
To prevent staging secrets during git commits, inspect git status and staged diffs before committing. Safety rules automatically avoid staging sensitive files, improving CI pipeline and code review reliability without bypassing hooks.
Using --no-verify or --amend is prohibited unless explicitly requested. This prevents unintentionally bypassing git hooks or altering existing commits, ensuring disciplined local development and reliable code review preparation.
Splitting large mixed-change commits into atomic semantic commits ensures each commit compiles and passes tests independently. This disciplined workflow makes changes easy to reason about, review, and revert during code review preparation.
Yes, the git commit workflow inspects git status and staged diffs before writing the commit message. It then groups related modifications and writes a concise subject with a descriptive body explaining why the change was made.
hb9397Generate Conventional Commits messages from staged git changes and project architecture.
0xharryriddlePrepare pull requests with atomic commits, conventional messages, and CI checks.
netresearchStandardize Git branching, commit conventions, and PR workflows across teams.
dipandhali2021Generate Conventional Commits messages by analyzing diffs and staging changes.
