git-helper

Guide Git version control with branching strategies and recovery techniques.

127|8|Updated Jun 14, 2022
One-click install
npx skills add https://github.com/shepherdjerred/monorepo --skill git-helper-shepherdjerred
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-helper
Source: https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_claude/skills/git-helper
Command: npx skills add https://github.com/shepherdjerred/monorepo --skill git-helper-shepherdjerred

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users navigate complex Git operations, understand best practices, and recover from common mistakes, ensuring efficient and safe version control.

Core Features & Use Cases

  • Advanced Operations: Provides guidance on interactive rebase, bisect, reflog, cherry-pick, and more.
  • Branching Strategies: Explains and contrasts Trunk-Based Development, GitHub Flow, and GitFlow.
  • Commit Best Practices: Enforces Conventional Commits and offers tips for atomic, clear commits.
  • Use Case: When a user is unsure how to clean up their commit history before a pull request, this Skill can guide them through an interactive rebase.

Quick Start

Use the git-helper skill to explain how to rebase a feature branch onto main.

Frequently Asked Questions about git-helper

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

FAQPage Schema
How do I clean up my commit history before a pull request using interactive rebase?

Interactive rebase lets you clean up commit history before a pull request by squashing, reordering, or editing commits. This Skill guides you through the rebase process step by step to ensure your branch history is atomic and clear.

What is the best way to resolve merge conflicts during a Git rebase?

Resolving merge conflicts during a Git rebase requires identifying conflicting changes, manually editing the files, and staging the resolutions. This Skill provides practical examples for safe conflict resolution and continuing the rebase.

How do Git branching strategies like GitFlow and Trunk-Based Development compare?

Git branching strategies like GitFlow and Trunk-Based Development differ in release management and branch longevity. This Skill explains and contrasts these workflows to help you choose the right strategy for your team's collaboration needs.

Can I recover lost commits in Git if I accidentally deleted a branch?

You can recover lost commits in Git using the reflog to find dangling history and restore deleted branches. This Skill covers advanced recovery techniques to safely retrieve and manage lost version control data.

Why should I use Conventional Commits in my version control workflow?

Conventional Commits standardize commit messages to ensure atomic, clear project history and facilitate automated tooling. This Skill enforces commit best practices to help you maintain efficient and readable code management.

When should I use git cherry-pick instead of merging a branch?

Git cherry-pick applies specific commits from one branch to another without merging the entire history. This Skill explains advanced operations like cherry-pick and when it is safer than a full branch merge for isolated changes.