git

Provide Git commands for staging, committing, branching, merging, and remote operations.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/zach-source/claude-plugins --skill git-zach-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/zach-source/claude-plugins/tree/main/plugins/git-tools/skills/git
Command: npx skills add https://github.com/zach-source/claude-plugins --skill git-zach-source

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance and commands for managing Git repositories, ensuring efficient version control and collaboration.

Core Features & Use Cases

  • Daily Workflow: Track changes, stage, commit, and view history.
  • Branching & Merging: Create, switch, delete branches, and resolve merge conflicts.
  • Rebasing & Undoing: Reapply commits, rewrite history safely, and recover from mistakes.
  • Remote Operations: Fetch, pull, push, and manage remote repositories.
  • Use Case: When you need to understand how to revert a commit that has already been pushed to a shared branch, this Skill will guide you through the git revert command and its implications.

Quick Start

Use the git skill to stage all changes in the current directory and commit them with the message "WIP".

Frequently Asked Questions about git

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

FAQPage Schema
How do I revert a commit that has already been pushed to a shared branch?

To revert a pushed commit, use the `git revert` command to create a new commit that undoes the specified changes, ensuring version control history remains intact for collaborative workflows.

What is the best way to resolve merge conflicts during branching and merging?

Resolving merge conflicts involves identifying conflicting changes between branches, manually editing the affected files to consolidate updates, and then staging the resolved files to complete the merging process.

How do I safely rewrite history when undoing changes with rebasing?

Safely rewrite history during rebasing by reapplying commits onto a new base, ensuring you only modify local branches to avoid disrupting remote repository interactions and shared version control workflows.

Can I manage remote repository interactions like fetch, pull, and push efficiently?

Yes, efficient remote operations involve using `git fetch` to retrieve updates, `git pull` to merge them locally, and `git push` to upload committed changes back to the remote repository.

When do I need to stage changes before committing in a daily workflow?

Staging changes is required before committing to selectively group modified files, allowing precise tracking of updates and ensuring only reviewed code enters the repository version control history.