skills.rest
yunseo-kim
yunseo-kimCOMMUNITY
Explore all skills by this author →
Website𝕏@yunse0_kimGitHub

git-master

Manage Git repository history with atomic commits, rebasing, and reflog recovery.

1|1|Updated Feb 15, 2026
Search Tags:#git#workflow#commit#refactor#history#recovery#rebase
One-click install
npx skills add https://github.com/yunseo-kim/agent-toolbox --skill git-master-yunseo-kim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/yunseo-kim/agent-toolbox/tree/main/.agents/skills/git-master
Command: npx skills add https://github.com/yunseo-kim/agent-toolbox --skill git-master-yunseo-kim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines Git operations by enforcing atomic commits, enabling safe history rewriting, and providing robust tools for recovering lost work, ensuring a clean and manageable project history.

Core Features & Use Cases

  • Atomic Commits: Enforces granular commits, splitting changes logically for clarity and easier review.
  • History Rewriting: Facilitates safe rebasing, squashing, and cherry-picking to maintain a linear and understandable commit history.
  • History Search & Recovery: Enables finding specific changes with blame, bisect, log -S, and recovering lost commits via reflog.
  • Use Case: When preparing a feature branch for a pull request, use this Skill to squash related commits, reorder them logically, and ensure each commit represents a single, testable change.

Quick Start

Use the git-master skill to clean up your current branch history by squashing and reordering commits.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I split a Git commit by directory to keep history atomic?▼

Atomic commits split changes logically by directory and concern to ensure a clean Git history. This approach breaks mixed changes into granular, testable commits paired with their implementations for easier review.

How do I safely rewrite Git history and rebase interactively?▼

Interactive rebase safely rewrites Git history by facilitating commit squashing, reordering, and cherry-picking. This maintains a linear, understandable history when preparing feature branches for pull requests.

How can I recover lost Git commits using reflog?▼

Recover lost Git commits via reflog by searching the history of reference updates. This recovery tool enables finding specific changes and restoring lost work even after history rewriting operations.

What is the best way to search Git history for a specific change?▼

The best way to search Git history for a specific change is using blame, bisect, and log -S. These search capabilities pinpoint exact modifications and identify when specific code was introduced.

Can I enforce semantic commit messages based on repository context?▼

Yes, you can enforce semantic or plain commit message styles based on repository context. The system evaluates repository context and enforces the appropriate commit message formatting for atomic commits.

When should I squash related commits before a pull request?▼

You should squash related commits before a pull request to ensure each commit represents a single, testable change. This maintains a linear, understandable history and makes the changes easier for reviewers to understand.

Related Skills

Explore More Software Engineering Skills→
jaqgjaqg

git-sync

Group modified and untracked files into logical git commits and print the command sequence.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
phraphra

code-review

Review modified code files and auto-fix mechanical issues.

Community
Advanced
FutureAtomsFutureAtoms
1

git-github-rebase

Perform interactive Git rebasing to squash, fixup, reword, reorder, or drop commits.

Community
Advanced