git-advanced-workflows

Optimize Git history via interactive rebasing, cherry-picking, and automated bisecting.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/AmidVoshakul/chatorai --skill git-advanced-workflows-amidvoshakul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-advanced-workflows
Source: https://github.com/AmidVoshakul/chatorai/tree/main/assets/skills/git-advanced-workflows
Command: npx skills add https://github.com/AmidVoshakul/chatorai --skill git-advanced-workflows-amidvoshakul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of maintaining a clean, professional Git history and provides a safety net for recovering from common version control mistakes.

Core Features & Use Cases

  • History Management: Perform interactive rebasing to squash, reword, or reorder commits for cleaner pull requests.
  • Advanced Recovery: Utilize reflog and worktrees to restore lost commits or manage multiple concurrent feature branches without context switching.
  • Debugging: Automate the identification of bug-introducing commits using binary search (bisect) workflows.

Quick Start

Use the git-advanced-workflows skill to interactively rebase the last five commits on your current branch to clean up your history.

Frequently Asked Questions about git-advanced-workflows

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

FAQPage Schema
How do I clean up my git history before creating a pull request?

Recover lost commits in git by utilizing the reflog to restore previous states. This skill provides advanced recovery workflows to safely retrieve accidentally deleted commits and manage repository history.

How do I find which commit introduced a bug using git bisect?

Manage multiple concurrent feature branches in git by utilizing worktrees. This skill facilitates complex development scenarios, allowing you to work on multiple branches without context switching.

Can I use this skill to cherry-pick commits across different branches?

Yes, this skill requires standard Git CLI tools to execute history manipulation and branch management operations. Ensure your environment includes the standard Git command-line interface.

What is the best way to squash multiple commits into one?

Avoid interactive rebasing on shared branches to prevent history conflicts. This skill is designed for complex branching and recovery, but standard rebasing limitations apply to shared repository history.