skills.rest
1thirteeng3
1thirteeng3COMMUNITY
Explore all skills by this author →
GitHub

git-master

Split changes into atomic commits and rewrite Git history safely.

Updated Mar 24, 2026
Search Tags:#automation#git#commits#history#version-control#rebasing
One-click install
npx skills add https://github.com/1thirteeng3/greenmoire --skill git-master-1thirteeng3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/oh-my-openagent/src/features/builtin-skills/git-master
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill git-master-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git Master Agent solves the challenge of maintaining clean, interpretable Git history across complex workflows by orchestrating atomic commits, history rewriting, and precise change tracking.

Core Features & Use Cases

  • Commit Architect: Atomic commits, dependency ordering, style detection
  • Rebase Surgeon: History rewriting, conflict resolution, branch cleanup
  • History Archaeologist: Finding when/where specific changes were introduced
  • Use cases: Preparing clean PRs, auditing when changes occurred, tracing regression sources

Quick Start

Invoke the git-master skill on your feature branch to automatically split changes into atomic commits, apply safe history rewrites when appropriate, and surface commit history insights before merging.

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 commits in git?▼

Atomic commits group related changes logically. This Skill orchestrates commit splitting by detecting dependencies and enforcing commit grouping rules, ensuring clean PRs and precise audit trails across multi-file changes.

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

Rewriting git history requires careful rebase strategies and conflict resolution. This Skill acts as a rebase surgeon, guiding safe history rewrites and branch cleanup to maintain merge-ready histories without losing critical changes.

How can I find when a specific change was introduced across git branches?▼

Finding when specific changes were introduced involves searching git history across branches. This Skill functions as a history archaeologist, tracing regression sources and auditing exactly where and when changes occurred.

Can I enforce a specific commit style before merging a feature branch?▼

Enforcing commit style is possible on feature branches. This Skill detects existing commit styles and applies rules around commit grouping, ensuring version-control hygiene and safe collaboration with merge-ready histories.

Why should I use atomic commits instead of a single large commit for my PR?▼

Atomic commits provide interpretable git history and precise audit trails. Unlike single large commits, this Skill separates dependency-ordered changes, making it easier to trace regression sources and prepare clean PRs.

Do I need any external git plugins to manage complex rebasing and history searches?▼

No external git plugins are required. This Skill operates independently to manage atomic commits, execute rebase strategies, and perform history searches across multi-file changes and branches without additional dependencies.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
alistairhendersoninfoalistairhendersoninfo

merge-pr

Merge GitHub pull requests after validating status, reviews, and CI results.

Community
Intermediate
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic
bmsull560bmsull560

jr-rebase

Resolves git rebase conflicts in feature branches via guided marker resolution.

Community
Intermediate