git-master

Automate Git workflows with atomic commits, rebasing, and history search.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces disciplined Git workflows by enabling atomic commits, safe history rewrites, and robust history exploration to improve traceability and code review quality.

Core Features & Use Cases

  • Atomic commits across related changes to keep history clean and reviewable.
  • Rebase/squash guidance for creating intentional, linear histories.
  • History search tools (blame, bisect, log -S) to locate when and where changes were introduced.
  • Clear guidance for commit-splitting and structuring changes by feature or directory.

Quick Start

Create a new branch, make changes across multiple files, and ensure commits are split by directory to maintain a clean, atomic history.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I split commits across multiple files to keep git history clean?

To split commits in git, you stage changes by directory or feature to create atomic commits. This keeps history reviewable and ensures related changes stay grouped. The git-master skill guides this process across multiple files and branches.

What is the best way to rewrite git history safely during rebasing?

Safe git history rewrites during rebasing require structured commit squashing and splitting. The git-master skill encodes operational constraints to guide rebase actions, ensuring intentional linear histories without losing track of changes.

How do I use git bisect and blame to locate when a change was introduced?

Git bisect and blame locate changes by searching commit history. Blame identifies the specific commit for a line, while bisect narrows down regression points. The git-master skill automates these investigations for precise history search.

How do I structure changes by directory for atomic commits in git?

Structuring changes by directory for atomic commits involves creating branches and staging related file modifications together. The git-master skill enforces multi-file commit governance to maintain clean, reviewable version-control history.

Can I use git-master for complex multi-branch rebasing workflows?

Yes, git-master supports complex multi-branch workflows. It provides automated planning and context-aware execution strategies for rebasing, commit splitting, and history exploration across multiple files and branches.