git-workflows

Name: git-workflows
Availability: InStock
Author: wewetv1987-cell

Resolve advanced Git workflow problems with rebasing, bisecting, worktrees, and reflog recovery.

Updated Feb 16, 2026

Search Tags:#git #worktree #reflog #rebase #conflict-resolution #bisect #version-control

Ready to run

npx skills add https://github.com/wewetv1987-cell/openclaw-backup --skill git-workflows-wewetv1987-cell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflows
Source: https://github.com/wewetv1987-cell/openclaw-backup/tree/main/skills/git-workflows
Command: npx skills add https://github.com/wewetv1987-cell/openclaw-backup --skill git-workflows-wewetv1987-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you handle advanced Git tasks that go beyond basic add, commit, and push workflows, especially when history needs cleanup, bugs must be traced, or work must be recovered after mistakes.

Core Features & Use Cases

History Cleanup: Reorder, squash, edit, or split commits before merging.
Bug Isolation and Recovery: Use bisect to find regressions and reflog to recover lost work.
Parallel and Large-Scale Development: Work with worktrees, cherry-pick across branches, manage submodules and subtrees, resolve conflicts, and use sparse checkout for monorepos.
Use Case: A developer can fix a broken release branch, recover a mistakenly reset commit, and prepare a clean feature history without creating extra clones.

Quick Start

Ask for help with a specific Git task such as rebasing a branch, recovering lost commits, or resolving a merge conflict in your repository.

Frequently Asked Questions about git-workflows

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

FAQPage Schema

How do I recover lost commits after a hard reset in Git?▼

Recover lost commits after a hard reset by using the Git reflog to trace previous HEAD positions and reset your branch back to the target reference. This Skill provides precise workflow guidance to restore mistakenly reset work.

What is the best way to isolate a regression bug in a large Git repository?▼

Isolate a regression bug in a large Git repository by using the Git bisect mechanism to binary search through your commit history. This Skill guides you through marking good and bad commits to pinpoint the exact breaking change.

How do I resolve complex merge conflicts during a Git rebase?▼

Resolve complex merge conflicts during a Git rebase by identifying conflicting files, editing them to reconcile differences, staging the resolutions, and continuing the rebase sequence. This workflow handles precise conflict resolution steps.

Can I work on multiple branches simultaneously without creating extra Git clones?▼

Work on multiple branches simultaneously without extra clones by using Git worktrees to manage parallel branch work. This approach allows you to checkout and develop on different branches in separate directories within the same repository.

How do I clean up and squash commits before merging a feature branch?▼

Clean up and squash commits before merging a feature branch by executing an interactive Git rebase to reorder, squash, edit, or split commits. This workflow prepares a clean feature history for merging into the main branch.

Does Git sparse checkout work for managing monorepo repositories?▼

Git sparse checkout works for managing monorepo repositories by allowing you to checkout only specific directories rather than the entire project tree. This workflow provides guidance for large-scale monorepo checkout scenarios.