git-master

Automate atomic commits, interactive rebasing, and branch history management.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/leejaedus/pepcode --skill git-master-leejaedus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/leejaedus/pepcode/tree/main/skills/git-master
Command: npx skills add https://github.com/leejaedus/pepcode --skill git-master-leejaedus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables precise and safe git operations like atomic commits, rebasing, and history cleanup to maintain clean project history.

Core Features & Use Cases

  • Atomic commits with conventional format
  • Interactive rebasing
  • Branch management
  • History cleanup
  • Style detection from repo history

Quick Start

Run git-master with your git task to perform atomic commits, interactive rebasing, and history management.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I automate atomic commits with conventional formats in git?

Automating atomic commits uses task-based routing to generate conventional commit formats, ensuring your git history remains structured and logically separated by task.

What is the best way to clean up git branch history?

The best way to clean up git branch history is through interactive rebasing and history management. This allows you to safely rewrite commits and maintain a controlled branch workflow.

Does git-master detect commit styles from existing repository history?

Yes, it detects commit styles directly from your existing repository history. This allows the skill to adapt its atomic commits and rebasing operations to match your project's established formatting.

Can I use interactive rebasing for software collaboration workflows?

Yes, interactive rebasing is fully supported for software collaboration workflows. It helps teams maintain a clean commit history and manage controlled branch workflows during shared project development.

When do I need interactive rebasing for version control?

You need interactive rebasing when your version control history requires cleanup or commit modification before merging. It is essential for maintaining atomic commits and a clean, readable project timeline.

Why does branch management require atomic commits?

Branch management requires atomic commits to ensure each change represents a single, logical update. This practice keeps the version control history clean and simplifies interactive rebasing during collaboration.