git-master

Automate atomic commits, interactive rebasing, and branch management in Git.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Atomic commits, clean rebasing, and deliberate history management to keep Git repos readable and maintainable.

Core Features & Use Cases

  • Atomic commits with conventional formats to ensure traceable history.
  • Interactive rebasing to reorder, squash, and fix commits without breaking history.
  • Branch management for feature, release, and hotfix workflows.
  • History cleanup to prune or rewrite problematic commits when needed.
  • Style detection from repository history to enforce consistency.

Quick Start

Ask git-master to perform an atomic commit on the current branch using a conventional format.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I create atomic commits with conventional formats in Git?

Atomic commits isolate single logical changes using conventional formats for traceable history. This automates staging and messaging to keep your repository clean and maintainable.

What is the best way to clean up Git history and rewrite problematic commits?

Cleaning Git history uses interactive rebasing to reorder, squash, or fix problematic commits. This ensures branch hygiene and maintains readability without breaking existing history.

How does interactive rebasing work for feature branch management?

Interactive rebasing reorders, squashes, and fixes commits on feature branches. It maintains deliberate history management by combining related updates before merging into the main branch.

Can I enforce consistent commit style by detecting patterns from repository history?

Style detection scans existing repository history to enforce consistency. It analyzes previous commit formats to automate future atomic commits matching your project conventions.

Does this work with hotfix and release branch workflows?

Branch management supports feature, release, and hotfix workflows. It automates robust Git operations across typical software projects to ensure clean history during team collaboration.