Create well-scoped git commits with Conventional Commits messages.
npx skills add https://github.com/guygrigsby/dotfiles --skill commit-work-guygrigsby
Please help me install this Agent Skill. Skill: commit-work Source: https://github.com/guygrigsby/dotfiles/tree/main/opencode/skills/commit-work Command: npx skills add https://github.com/guygrigsby/dotfiles --skill commit-work-guygrigsby
Creating git commits that are easy to review and safe to merge by ensuring only the intended changes are included, dividing work into logical commits, and writing clear, conventional messages.
Inspect the working tree, stage changes selectively with patch mode, craft conventional commit messages, and verify each commit before finishing.
High-intent search queries and answers about installing and using this skill.
Split mixed changes into logical git commits by using patch staging (-p) to selectively group related modifications. This separates features from refactors or tests from production code to produce precise, review-ready commits.
Conventional Commits enforce a standard type and scope in git commit messages to improve traceability and automation. You need them when preparing review-ready commits that require clear, structured formatting for safe merging.
Prevent secrets and debug logs from being committed by running automated safety and quality checks before finalizing. These checks scan your staged changes to block risky commits containing sensitive data or unrelated formatting changes.
The best way to stage specific lines for a git commit is using patch staging (-p). This allows fine-grained control to guide staging only what belongs in the next commit and verifying with diffs before finishing.
Yes, you can use patch staging to prepare commits for code review by polishing messages and dividing work into logical commits. This ensures only intended changes are included, making commits easy to review and safe to merge.
Verify git diffs before finalizing a commit to ensure only intended changes are included. This verification step prevents unrelated formatting changes and debug statements from slipping into your logical, review-ready commits.
t-miura-024Analyze git repository changes and retrieve detailed diffs for modified files.
tapanshahGenerate markdown and JSON changelog entries from Conventional Commits.
julianobarbosaReview code for quality, bugs, security issues, and best practices using Codex.
paywherebSquash all branch commits into one via interactive git rebase.
