git-master

Plan atomic commits, rewrite git history, and trace changes with safety checks.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/CNife/skills --skill git-master-cnife
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/CNife/skills/tree/main/.archive/git-master
Command: npx skills add https://github.com/CNife/skills --skill git-master-cnife

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork from git history work by helping you create clean commits, rewrite branches safely, and investigate when changes appeared.

Core Features & Use Cases

  • Atomic commit planning: Splits multi-file changes into focused commits with dependency-aware ordering.
  • History rewriting: Handles rebases, squashes, autosquash fixups, and branch cleanup with safety checks.
  • History forensics: Finds the commit that introduced a change using blame, pickaxe searches, and bisect workflows.

Quick Start

Use the git-master skill to analyze my current branch and perform the git operation I asked for with the correct workflow and safety checks.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I safely squash commits and rebase a branch without losing changes?

Squashing commits and rebasing branches safely requires analyzing the branch state, planning atomic commits, and running rewrite safety checks before execution to ensure no changes are lost during history rewriting.

How do I find which commit introduced a specific change in my repository?

Finding the commit that introduced a change involves using git history forensics workflows like blame lookups, pickaxe searches, and bisect investigations to trace exactly when and where the modification appeared in the code.

What is the best way to split multi-file changes into focused atomic commits?

Splitting multi-file changes into atomic commits requires dependency-aware ordering and commit style detection to organize staged files into focused, logical units that keep the repository history clean and readable.

Can I use autosquash fixups to clean up git history automatically?

Autosquash fixups can clean up git history by reordering and squashing designated fixup commits into their targets, requiring branch-state analysis and clean verification before execution to confirm the rewrite is safe.

Why do I need to verify my branch state before rewriting git history?

Verifying branch state before rewriting git history is necessary to perform safety checks that prevent data loss, ensuring the working tree is clean and the rebase or squash operation will execute without conflicts.