skills.rest
maximhar
maximharCOMMUNITY
Explore all skills by this author →
GitHub

git-master

Manage Git operations with atomic commits, rebase, squash, and history search.

1|Updated Feb 14, 2026
Search Tags:#git#commit#history#rebase#bisect#blame
One-click install
npx skills add https://github.com/maximhar/oh-my-opencode-beads --skill git-master-maximhar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/maximhar/oh-my-opencode-beads/tree/main/src/features/builtin-skills/git-master
Command: npx skills add https://github.com/maximhar/oh-my-opencode-beads --skill git-master-maximhar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines Git operations by enforcing atomic commits, enabling efficient history rewriting, and providing powerful tools for searching and understanding your project's history.

Core Features & Use Cases

  • Atomic Commits: Ensures commits are small, focused, and easily understandable.
  • History Rewriting: Facilitates rebasing, squashing, and cleaning up commit history.
  • History Search: Allows finding specific changes, authors, or when features were introduced using blame, bisect, and log searching.
  • Use Case: When you've made several related changes, this Skill helps you split them into multiple, clean commits instead of one large, messy one, making code reviews and rollbacks much easier.

Quick Start

Use the git-master skill to commit your staged changes with atomic best practices.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I split a large commit into smaller atomic commits in Git?▼

To split a large commit into atomic commits, this Skill stages related changes and creates multiple focused commits, enforcing commit atomicity and dependency ordering for easier code reviews and rollbacks.

What is the best way to squash and rewrite Git commit history?▼

The best way to rewrite Git history is using this Skill to facilitate safe rebasing and squashing, cleaning up your commit history while enforcing safe history manipulation practices across various Git modes.

How does Git bisect work for finding when a bug was introduced?▼

Git bisect works by performing a binary search through your commit history, and this Skill uses bisect, blame, and log analysis to find specific changes, authors, or when features were introduced.

Can I use Git blame to search for specific code changes and authors?▼

Yes, you can use Git blame to search for specific changes and authors, as this Skill provides in-depth history searching using blame, bisect, and log analysis to understand your project history.

When should I rebase my Git commits instead of merging?▼

You should rebase Git commits when you need to rewrite or clean up commit history, as this Skill facilitates rebasing, squashing, and safe history manipulation to maintain a understandable project timeline.

Are there limitations to rewriting Git history with rebase and squash?▼

Limitations of rewriting Git history involve potential risks, but this Skill enforces best practices for safe history manipulation and dependency ordering across various Git modes to mitigate those risks.

Related Skills

Explore More Software Engineering Skills→
blakecyzeblakecyze
2

kanso-commit

Analyze the working tree and create atomic git commits with imperative messages.

Community
Intermediate
Jst-Well-DanJst-Well-Dan
8

git-pushing

Stage, commit, and push git changes with conventional commit messages.

Community
Intermediate
cipherstashcipherstash
17

Commit Workflow

Run pre-commit checks and create atomic conventional commits.

Official
Intermediate
gjkellergjkeller
2

git-master

Manage Git operations with atomic commits, history rewriting, and advanced searching.

Community
Advanced