git-master

Coordinate atomic commits, structured rebasing, and precise git history searches.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/phar-dev/phardev.dot --skill git-master-phar-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/phar-dev/phardev.dot/tree/main/opencode/.config/opencode/skills/git-master
Command: npx skills add https://github.com/phar-dev/phardev.dot --skill git-master-phar-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git operations can devolve into confusion without atomic commits, disciplined history, and reliable search tools. This skill provides a structured approach to performing git actions with atomic commits, safe rebasing, and robust history exploration to keep project histories clean and auditable.

Core Features & Use Cases

  • Commit Architect: Atomic commits, dependency ordering, style detection for messages.
  • Rebase Surgeon: History rewriting, conflict resolution guidance, branch cleanup.
  • History Archaeologist: Finding when/where changes were introduced via blame, log, and bisect.
  • Use Case: Split a feature into multiple focused commits and rebase cleanly onto main while preserving traceable history.

Quick Start

Instruct the agent to manage a git workflow using atomic commits, safe rebases, and history searches with git-master.

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 feature branch into atomic commits with dependency ordering?

To create atomic commits, group changes by logical dependency and apply style-detected commit messages. This ensures deterministic, auditable project histories with focused, traceable feature commits.

What is the safest way to rebase feature branches onto main while resolving conflicts?

Safe rebasing requires controlled history rewriting with explicit conflict resolution guidance and branch cleanup. This preserves traceable project history while integrating feature branches cleanly onto the main branch.

How do I use git bisect and blame to find when a bug was introduced in commit history?

Git bisect and blame identify exactly when and where changes were introduced. Running robust history analysis with these tools pinpoints the specific commit responsible for introducing a bug.

Why does my git history become confusing and how do I enforce clean project commits?

Git history becomes confusing without atomic commits and disciplined search tools. Enforcing explicit commit grouping, controlled rebasing practices, and structured history exploration keeps histories clean and auditable.

Can I use this git workflow automation for team collaboration on feature branches?

Yes, this workflow suits software development teams needing reliable blame, bisect, and safe collaboration on feature branches. It enforces guardrails and prompts for deterministic, auditable project histories.

Are there limitations to rewriting git history with structured rebasing?

History rewriting limitations depend on controlled rebasing practices and guardrails. You should not use uncontrolled rebasing on shared branches, as it can disrupt team collaboration and break traceable project history.