git-master

Automate atomic commits, rebases, and history searches in Git workflows.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/nous-labs/oh-my-opencode --skill git-master-nous-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/nous-labs/oh-my-opencode/tree/main/src/features/builtin-skills/git-master
Command: npx skills add https://github.com/nous-labs/oh-my-opencode --skill git-master-nous-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces rigorous Git workflows by enabling atomic commits, safe history rewriting, and efficient history searches, reducing the risk of messy histories and accidental data loss.

Core Features & Use Cases

  • Atomic commits: group related changes into independent, reviewable units.
  • Rebase & squash guidance: maintain a clean, chronological project history.
  • History search: quick access to blame, bisect, and -S/-G diff queries to trace changes.
  • Use Case: when fixing a bug across multiple files, this Skill ensures changes are split into focused commits and properly documented.

Quick Start

Before performing complex git operations, initialize git-master to guide atomic commits and safe history edits.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I split changes into atomic commits in git?

Atomic commits group related changes into independent, reviewable units. This Skill automates the grouping process, guiding you from an initial plan to focused, properly documented commits that ensure traceable changes across multiple files.

What is the best way to perform a safe git rebase and squash?

Safe git rebase and squash operations maintain a clean, chronological project history. This Skill provides controlled rebase guidance, enforcing structured checks and prompts to prevent accidental data loss during history rewriting.

How do I trace when a bug was introduced using git history search?

Git bisect traces regressions by binary searching commit history. This Skill automates blame and bisect queries, alongside -S/-G diff searches, to quickly pinpoint when and how specific changes were introduced.

Can I use this to guide git workflows for a multi-file bugfix?

Yes, when fixing a bug across multiple files, this Skill ensures changes are split into focused, atomic commits and properly documented. It orchestrates the entire workflow from planning to a clean, auditable history.

Why should I enforce atomic commits and controlled rebases?

Enforcing atomic commits and controlled rebases reduces the risk of messy histories and accidental data loss. It ensures safe history rewriting and produces a clean, auditable project history with traceable changes.