committing-changes

Enforce git-spice commands for branch creation, commits, and amendments.

13|6|Updated Feb 23, 2013
One-click install
npx skills add https://github.com/abhinav/home --skill committing-changes
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: committing-changes
Source: https://github.com/abhinav/home/tree/main/.claude/skills/committing-changes
Command: npx skills add https://github.com/abhinav/home --skill committing-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and simplifies complex Git operations like committing, branching, and amending, preventing common errors and ensuring a clean, organized version control history. It replaces raw Git commands with a guided, intelligent workflow.

Core Features & Use Cases

  • Intelligent Branching: Automatically creates new feature branches or stacks them on existing ones, based on your current Git state.
  • Standardized Commits: Guides the use of git-spice for consistent commit messages and operations, integrating with the writing-commits Skill.
  • Safe Amending: Provides a clear process for amending the last commit, with or without changing the message.
  • Use Case: When developing a new feature, use this Skill to automatically create a new feature branch, commit your changes with a properly formatted message, and amend previous commits without manually remembering complex git commands.

Quick Start

Create a new feature branch with a commit message

gs branch create my-feature-branch -m "feat: Add new user profile page"

Commit changes to the current branch

gs commit create -m "fix: Resolve styling issues on profile page"

Amend the last commit with staged changes

gs commit amend

Frequently Asked Questions about committing-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Git commits and branching across my development workflow?ā–¼

This Skill standardizes Git operations by enforcing git-spice commands for commits, branching, and amendments. It automatically creates feature branches with lowercase-hyphen naming, guides commit messages through integration with commit-message workflows, and provides safe amendment processes to prevent common Git errors and maintain organized version control history.

What's the best way to create and stack feature branches in Git?ā–¼

Use git-spice branch creation to automatically generate new feature branches or stack them on existing ones based on your current Git state. The Skill handles branch naming normalization to lowercase-hyphen format and integrates branch creation with standardized commit messaging for a guided, consistent workflow.

How do I amend commits safely without losing work or breaking my branch history?ā–¼

This Skill provides a clear amendment process for modifying the last commit with or without changing the message. It enforces git-spice commands to manage amendments safely across stacked branches, preventing accidental loss of changes and maintaining clean branch history during development.

Can I use git-spice commands to replace manual Git operations in my workflow?ā–¼

Yes. This Skill replaces raw Git commands with guided git-spice operations for branching, committing, and amending. It enforces lowercase-hyphen branch naming, normalizes non-conforming names automatically, and integrates with commit-message workflows to simplify complex Git operations and reduce manual command errors.

What happens when I create a commit with inconsistent naming or messages?ā–¼

The Skill enforces automated normalization of branch names to lowercase-hyphen format and guides commit messages through integration with the writing-commit-messages workflow. Non-conforming names are automatically normalized, preventing mismanagement and ensuring all commits follow standardized conventions.

Does this work for quick fixes and emergency commits during active development?ā–¼

Yes. The Skill applies to all commit-related tasks, including quick commits and emergency fixes in typical development scenarios. It enforces git-spice usage consistently across routine commits, amendments, and branch operations to maintain workflow standardization even during urgent changes.