// Use when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current branch, or recovering after raw Git commands. Load and follow the git-spice skill for the workflow.
| name | commit |
| description | Use when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current branch, or recovering after raw Git commands. Load and follow the git-spice skill for the workflow. |
Use the git-spice skill to commit,
amend,
fix up,
branch,
or stack work exactly as described there.
For any commit, branch-as-part-of-commit, stacking, or raw-Git-recovery task, first load and follow:
~/.agents/skills/git-spice/SKILL.md
That skill is the authoritative manual for:
For commit message writing, the canonical reference is:
~/.agents/skills/git-spice/references/writing-commit-messages.md
Do not invent a separate commit workflow here.
Load git-spice,
then perform the commit operation exactly as that skill describes.
Use when creating or updating skills, testing skill behavior with subagents, repairing unclear triggers or observed misbehavior, designing pressure tests, closing loopholes, addressing rationalizations, or validating skill folders before deployment.
Mandatory for Git repository operations involving commits, amendments, fixups, branch creation or movement, stacked branches, pushes, pull request creation, pull request updates, review submission, publishing, or recovery from raw Git usage. Use git-spice for supported operations; do not bypass git-spice for commits, branches, stack movement, pushes, or pull request submission.
Use when creating pull requests, updating pull request branches, pushing or publishing work for review, editing pull request metadata, or submitting stacked branches. Load and follow the git-spice skill for the workflow.
Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`.