git-master

Organize multi-file Git changes into atomic commits with rebase and squash workflows.

1|Updated Aug 25, 2024

Search Tags:#git #commits #history #squash #bisect #blame #rebases

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 대규모 Git 변경을 원자 커밋으로 분할하고, 리베이스/스쿼시를 통해 히스토리를 깔끔하게 관리하며 변경 이력을 추적하는 과정을 자동화합니다.

Core Features & Use Cases

Atomic commit 분할: 다수 파일 변경을 독립적인 커밋으로 나눕니다.
Rebase / Squash: 히스토리 재작성 및 브랜치 정리가 가능합니다.
History 탐색: blame, bisect를 통해 특정 변경이 도입된 시점과 원인을 파악합니다.

Quick Start

간단 예시: 현재 변경을 원자 커밋으로 분할하고, 필요 시 히스토리를 조회합니다.

예: 다수 파일 변경을 각 커밋으로 나누고, 이후 git blame으로 특정 변경의 책임자를 추적합니다.

Frequently Asked Questions about git-master

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

FAQPage Schema

How do I split multi-file changes into atomic git commits?▼

To split multi-file changes into atomic git commits, this Skill automates the organization of changes into independent commits, enforcing commit discipline and traceability using standard Git tooling across branches.

What is the best way to clean up git history with rebase and squash?▼

The best way to clean up git history is by using rebase and squash workflows, which this Skill automates to rewrite history and organize multi-file changes into clear, independent atomic commits.

How does git bisect and blame work for tracking specific changes?▼

Git bisect and blame work by navigating history to pinpoint when and why a specific change was introduced; this Skill automates blame and bisect workflows to track traceability across branches.

Can I use this for managing git history across multiple branches?▼

Yes, you can use this for managing git history across multiple branches, as it applies atomic commit splitting, rebasing, squashing, and blame workflows across branches using standard Git tooling.

When do I need to organize changes into atomic commits?▼

You need to organize changes into atomic commits when managing large-scale Git changes, ensuring independent commits enforce commit discipline and traceability before performing complex rebases or history exploration.

Does git-master work without additional dependencies or components?▼

Yes, git-master works without additional dependencies or components, automating Git history management using standard Git tooling for atomic commits, rebases, and history exploration.