git-master

Automate advanced Git workflows including atomic commits, rebasing, and history search.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/opzero1/op1 --skill git-master-opzero1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/opzero1/op1/tree/main/packages/install/templates/skill/git-master
Command: npx skills add https://github.com/opzero1/op1 --skill git-master-opzero1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers implement and manage advanced Git workflows with confidence, from crafting atomic commits to precise history exploration.

Core Features & Use Cases

  • Atomic commits with clear messages and single-purpose changes
  • Rebasing, squashing, and maintaining a clean project history
  • History search capabilities (blame, bisect, log -S) and inquiries like "who wrote" or "when was X added"

Quick Start

Use this skill to guide a complex Git operation like rewriting history for a feature branch.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I squash commits and rebase a feature branch safely?

To squash commits and rebase a feature branch safely, this Skill automates the workflow to rewrite history cleanly. It ensures a repeatable project history by combining single-purpose atomic commits using standard Git commands.

What are atomic commits in Git and when should I use them?

Atomic commits are single-purpose, self-contained changes with clear messages. You should use them to maintain a clean project history, ensuring each commit represents one logical modification that is safe to rebase or revert.

How do I find when a specific line of code was added using Git history search?

To find when code was added, use Git history search capabilities like blame, bisect, and log -S. These commands allow you to execute precise inquiries such as 'who wrote' a line or 'when was X added' across complex projects.

Does this Git workflow automation work without installing extra dependencies?

Yes, the Git workflow automation works without extra dependencies. It relies entirely on standard Git commands and documented guidelines to provide safe, repeatable operations for complex project version control.

What is the best way to maintain a clean project history across complex repositories?

The best way to maintain a clean project history is combining atomic commits with regular rebasing and squashing. This approach prevents tangled logs and enables accurate history exploration through blame and bisect queries.

Can I use Git bisect to track down when a bug was introduced in a complex project?

Yes, you can use Git bisect to track down when a bug was introduced. The history search capabilities support bisect and log -S, allowing you to perform precise 'when was X added' queries across complex project histories.