Group dirty Git working tree changes into logically structured commits.
npx skills add https://github.com/sunsided/commit-skills --skill commit-sunsided
Please help me install this Agent Skill. Skill: commit Source: https://github.com/sunsided/commit-skills/tree/main/commit Command: npx skills add https://github.com/sunsided/commit-skills --skill commit-sunsided
This Skill helps you convert a messy working tree into a set of logically grouped, well-written commits that a reviewer can understand quickly and safely.
git add, avoids committing secrets, and asks for confirmation when boundaries are ambiguous.Ask the AI to commit your current changes with commit messages that match this repository’s style, splitting unrelated work into separate commits and including reviewer-oriented explanations and any relevant issue links.
High-intent search queries and answers about installing and using this skill.
To split dirty Git changes into clean commits, the tool reads your working tree diffs, detects logical groupings by intent, stages explicit file lists, and writes reviewer-friendly messages. It then asks for your approval before executing the commits.
You can write conventional commit messages that match your history by analyzing recent Git log entries and policy files. The tool auto-detects your repository's commit convention and generates imperative-style or ticket-prefixed messages accordingly.
The best way to group code changes before a pull request is to separate unrelated work into distinct commits while keeping tightly coupled changes, including tests and wiring, together in a draft commit plan for user review.
To extract issue links from Git branches and include them in commit bodies, the tool optionally parses branch names, diffs, and history. It then surfaces these issue links within the extended rationale-focused message body.
Yes, you can commit specific file refactors safely because the tool uses explicit file lists for git add and avoids committing secrets. It asks for confirmation when boundaries are ambiguous to prevent unsafe artifacts.
ajbareaGenerate a conventional-commit plan for pending git changes in COMMITS.md.
omeraltnEnforce conventional commits and safe Git workflows across team repositories.
jtucker9Verify completed work with automated build, test, and lint checks before committing.
borkwebGenerate conventional git commit messages from staged diffs and repository history.