committing

What problem does it solve?

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.

Core Features & Use Cases

• Discipline for commits: All commits are created via gs commands and messages are generated by Skill(writing-commit-messages).
• Branch stacking: Creating new branches automatically stacks on the current feature branch when applicable.
• Never use raw Git: Replaces git commit, git checkout -b, and git branch with git-spice commands.

Quick Start

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.