Create logically scoped git commits with Conventional Commit messages from working-tree changes.
npx skills add https://github.com/Soyio-id/skills --skill commit-work-soyio-id
Please help me install this Agent Skill. Skill: commit-work Source: https://github.com/Soyio-id/skills/tree/main/skills/commit-work Command: npx skills add https://github.com/Soyio-id/skills --skill commit-work-soyio-id
This Skill helps developers transform a messy set of working-tree changes into a small set of logically scoped, reviewable commits with clear Conventional Commit messages, reducing review friction and shipping risk.
Inspect the repository changes, stage related hunks into separate commits using patch staging, and write Conventional Commit messages that describe what changed and why.
High-intent search queries and answers about installing and using this skill.
Split mixed changes by inspecting working tree diffs and using hunk-level patch staging to group related modifications into separate commits. This creates logically scoped commits that reduce review friction and shipping risk.
A conventional commit message follows the type(context): description format to indicate the nature of changes. It summarizes what changed and why, providing a standardized commit history that makes code review and automation more efficient.
Stage specific hunks instead of entire files by using git patch staging tools to selectively add modified sections. This allows you to separate unrelated edits, formatting changes, and tests into distinct commits for clearer reviews.
Yes, you can run quick repository verification checks before finalizing your git commit. Running these checks ensures the staged changes do not break existing functionality and that tests accompany the corresponding code modifications.
The best way to handle unrelated edits and formatting churn is to inspect status checks and diffs to identify them, then isolate them using selective hunk staging. This separates formatting-only changes from functional code changes for cleaner commits.
rcdaileyStage specific Git hunks by stable ID for atomic commits.
bdsqqqStage modified files, commit with conventional commits, and push to the remote repository.
AmidVoshakulAutomate Git hook configuration for linting, formatting, and commit message validation.
ebknStage and commit changes with conventional messages and logical grouping.
