skills.rest
tc9011
tc9011COMMUNITY
Explore all skills by this author →
WebsiteGitHub

Git Master Agent

Manage Git commits, rebase branches, and analyze repository history.

Updated Feb 5, 2026
Search Tags:#git#code review#version control#commit#history#rebase
One-click install
npx skills add https://github.com/tc9011/my-skills --skill git-master-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git Master Agent
Source: https://github.com/tc9011/my-skills/tree/main/skills/git-master
Command: npx skills add https://github.com/tc9011/my-skills --skill git-master-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines Git operations by enforcing atomic commits, intelligently rewriting history, and providing deep insights into past changes, ensuring a clean and understandable project history.

Core Features & Use Cases

  • Atomic Committing: Enforces granular commits, splitting changes by directory, component, or concern to improve code review and revertability.
  • Intelligent Rebasing: Handles complex history rewriting, conflict resolution, and branch cleanup with clear strategies.
  • History Analysis: Enables deep dives into commit history to find when and why specific changes were introduced.
  • Use Case: Before merging a large feature, use this Skill to break down your work into a series of small, logical commits, ensuring each commit is reviewable and testable independently.

Quick Start

Use the git master agent to analyze your current branch and plan atomic commits for your staged changes.

Frequently Asked Questions about Git Master Agent

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

FAQPage Schema
How do I split staged changes into atomic commits?▼

Git history analysis identifies when and why specific changes or bugs were introduced by performing deep dives into commit history across the entire repository, tracing the introduction of specific code patterns.

What is the best way to rewrite git history and resolve conflicts?▼

Rewriting git history safely requires planning strategies for aggressive or safe rebasing, handling complex history rewriting, and executing branch cleanup while managing conflict resolution during the process.

How do I find when a specific code pattern or bug was introduced in git history?▼

Git history analysis identifies when and why specific changes or bugs were introduced by performing deep dives into commit history across the entire repository, tracing the introduction of specific code patterns.

Can I automatically detect commit style and language for my repository?▼

Automatic detection of commit style and language is supported by analyzing your current branch and staged changes to enforce atomic commit principles and maintain a clean, understandable project history.

When should I avoid aggressive history rewriting in version control?▼

Aggressive history rewriting should be avoided when maintaining shared branch integrity, whereas safe history rewriting strategies are suitable for local branch cleanup and resolving conflicts before merging features.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
lucasfloreslucasflores

commit-pipeline

Automate git commit workflows with dev-stack pipeline integration and Copilot review.

Community
Advanced
lehuuhau1231lehuuhau1231

lint-and-validate

Run linting and type checking across multiple programming ecosystems.

Community
Intermediate
joegoldinjoegoldin
2

git-hunk

Stage, unstage, and inspect Git hunks by hash non-interactively.

Community
Intermediate