git-master

Guide atomic commits, rebases, and history searches in Git.

1|Updated Sep 11, 2023

Search Tags:#git #commits #history #bisect #blame #rebasing

Ready to run

npx skills add https://github.com/vcntttt/dotfiles --skill git-master-vcntttt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/vcntttt/dotfiles/tree/main/.agents/skills/git-master
Command: npx skills add https://github.com/vcntttt/dotfiles --skill git-master-vcntttt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The git-master skill helps developers enforce high-quality Git history by guiding atomic commits, structured rebases, and efficient history searches.

Core Features & Use Cases

Atomic commits: ensure changes are split logically across commits.
Rebase surgery and history archaeology: clean up commits, squash, fixup, and prune history; find when changes were introduced.
History search: use blame, bisect, and log -S to locate authors and points of change.

Quick Start

To begin, describe the Git operation you want (commit, rebase, or search) and let the skill guide the steps, including how to split changes, perform rebases, or locate the origin of a change.

Frequently Asked Questions about git-master

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

FAQPage Schema

How do I split changes across multiple files into atomic commits in Git?▼

Atomic commits in Git are created by logically splitting changes across multiple files. The skill guides developers through the workflow of separating changes into focused, self-contained commits on any branch.

What is the best way to squash or fixup commits during a Git rebase?▼

Squashing or fixup commits during a Git rebase is performed through history surgery to clean up and prune history. The skill provides explicit guidance for restructuring commits and performing rebases.

How do I locate the origin of a change in my Git history?▼

Locating the origin of a change in Git history is done using blame, bisect, and log -S searches. The skill helps find when changes were introduced and identify the authors of specific modifications.

Can I use this Git history workflow on any branch?▼

Yes, the Git history workflow applies to any branch. It requires no external tools beyond Git and supports daily development tasks like atomic commits, squashes, blame, and bisect scenarios.

When should I not use interactive rebasing for history cleanup?▼

Interactive rebasing for history cleanup should not be used on shared branches where it rewrites published history. It is best applied to local history surgery for squashing and splitting commits before integration.