Create git commits with structured Problem and Solution messages.
npx skills add https://github.com/hujw77/dotfiles --skill commit-hujw77
Please help me install this Agent Skill. Skill: commit Source: https://github.com/hujw77/dotfiles/tree/main/home/.config/claude/skills/commit Command: npx skills add https://github.com/hujw77/dotfiles --skill commit-hujw77
This skill provides a disciplined workflow for committing changes by enforcing a structured commit message format and safe branch handling, reducing ambiguity and drift in version history.
Ask me to commit your current changes with a concise title and a Problem/Solution body, creating an echo/ branch if you are on main or master.
High-intent search queries and answers about installing and using this skill.
A structured git commit message requires a short title prefix and a two-part body detailing the Problem and Solution. This format improves traceability and review efficiency by clearly separating the issue addressed from the fix applied.
To commit changes safely, the workflow checks your current branch and creates a new echo/ prefixed branch if you are on main or master. This prevents direct commits to protected branches and ensures changes are isolated for review.
The best way to include all related files is to use git add for every file associated with your change before committing. This ensures complete file coverage and prevents partial commits that could break the version history.
No, you should not include test changes in the git commit message description. Commit guidelines recommend writing clearly and avoiding unnecessary complexity by excluding test details from the Problem and Solution body.
Yes, you can use this workflow to create a changelog entry across different branches. It automates well-formed commits with structured messages and enforces branch-handling rules, ensuring consistent history regardless of the active branch.
A limitation of automating git commits with a structured message is the strict enforcement of a two-part Problem and Solution body. This rigid format may not suit trivial changes and requires all related files to be added manually.
mgoodman60Generate descriptive Git commit messages from repository changes with conventional formatting.
bswrundquistPush local commits to a remote Git repository with safety checks.
genesis-agentsImplement Git workflow conventions and CI checks for GenesisPod projects.
sulhicmzGenerate conventional commit messages from git diffs and staged changes.
