Enforce git-spice commands for commits and branch stacking.
npx skills add https://github.com/abhinav/home --skill committing-abhinav
Please help me install this Agent Skill. Skill: committing Source: https://github.com/abhinav/home/tree/main/.claude/skills/committing Command: npx skills add https://github.com/abhinav/home --skill committing-abhinav
This Skill prevents drift in Git workflows by enforcing the use of git-spice for all commits and branch operations, preserving stack history and automatic rebasing. It also ensures commit messages are generated by the writing-commit-messages skill and avoids raw git usage that leads to broken histories.
gs commands and messages are generated by Skill(writing-commit-messages).git commit, git checkout -b, and git branch with git-spice commands.Before committing, load Skill(writing-commit-messages) to craft a proper message, then run: gs branch create <branch-name> -m "<message>" or gs commit create -m "<message>". When amending, use gs commit amend as needed.
High-intent search queries and answers about installing and using this skill.
Enforce git-spice commits by replacing raw git commands with `gs commit create` and `gs branch create` for all commit and branching operations. This Skill prevents stack tracking drift and maintains automatic rebasing of dependent branches, keeping your history intact across collaborative sessions.
Git-spice (`gs`) preserves stack history and auto-rebases dependent branches, while raw git commands like `git commit` and `git checkout -b` break stack tracking and cause history divergence. This Skill enforces `gs` workflows to maintain consistent branch relationships.
Yes. This Skill applies to all commit workflows—creating, amending, and stacking branches—whether single-user or collaborative. It replaces raw git usage with standardized `gs` commands and integrates with the writing-commit-messages Skill for consistent messaging.
This Skill provides recovery from prior raw git usage by enforcing `gs` for all future commits and branch operations. It prevents further history divergence and restores stack tracking, though you should use `gs` commands exclusively going forward.
Yes. This Skill requires the writing-commit-messages Skill to generate proper commit messages before running `gs commit create -m` or `gs branch create -m`. Load that Skill first to craft messages that align with your workflow standards.
New branches automatically stack on the current feature branch when applicable, maintaining the branch hierarchy. Git-spice then auto-rebases dependent branches, ensuring your stack remains consistent without manual intervention.
abhinavEnforce git-spice commands for branch creation, commits, and amendments.
luanSync a Git-Spice repository with its remote trunk and clean merged branches.
luanAutomates Git-Spice stacked workflows to create, navigate and submit Change Requests.
binoy14Automate stacked git branches and dependent pull requests with git-spice CLI.