git-master

Plan, execute, and enforce atomic git commits with safety checks.

1|Updated Mar 12, 2026

Search Tags:#automation #git #workflow #commit #history #version-control #rebasing

Ready to run

npx skills add https://github.com/lifeodyssey/opencode-team-config --skill git-master-lifeodyssey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/lifeodyssey/opencode-team-config/tree/main/skills/git-master
Command: npx skills add https://github.com/lifeodyssey/opencode-team-config --skill git-master-lifeodyssey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to maintain clean, atomic commits and a trustworthy history when making complex changes across multiple files and branches. This Skill provides a structured, multi-phase approach to plan, validate, and execute git operations—ensuring each commit is focused, tests are paired, and history remains readable and safe to rewrite when appropriate.

Core Features & Use Cases

Enforces atomic commits by splitting changes into small, reviewable units that map to specific features or fixes.
Provides a robust framework for commit planning, test pairing, and safe history editing (rebases, resets) on feature branches.
Helps teams coordinate complex workflows (rebases, squashes, bisects) with guardrails to prevent accidental data loss.

Quick Start

Plan your git operations by outlining the intended commits and affected files, then execute the guided workflow.

Frequently Asked Questions about git-master

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

FAQPage Schema

How do I split complex multi-file changes into atomic git commits?▼

To split complex multi-file changes into atomic git commits, this Skill analyzes your working tree and generates a structured commit plan that maps changes to specific features or fixes. It enforces a multi-phase workflow to ensure each commit remains a focused, reviewable unit.

What is the safest way to rebase and squash commits on a feature branch?▼

The safest way to rebase and squash commits on a feature branch is using a structured workflow with built-in guardrails. This Skill executes history editing through analysis, planning, and verification phases to prevent accidental data loss and maintain history hygiene.

How do I enforce test pairing when planning git commits?▼

To enforce test pairing when planning git commits, this Skill integrates test validation into its commit execution phase. It ensures every planned atomic commit is checked against corresponding tests before history is finalized, aligning outcomes with project conventions.

Can I force-push rebased history safely without losing collaboration work?▼

You can force-push rebased history safely because this Skill provides built-in guardrails for force-push operations and collaboration. It enforces strict verification phases during history edits to prevent accidental data loss on shared feature branches.

Does this git workflow automation handle complex multi-file version control changes?▼

Yes, this git workflow automation handles complex multi-file version control changes by enforcing an atomic commit planning process. It analyzes the changes, generates a reproducible commit plan, and validates the execution to maintain a trustworthy history.

When should I avoid using automated git rebasing strategies?▼

You should avoid using automated git rebasing strategies on branches where collaboration guardrails cannot be enforced or when commit verification fails. The Skill's multi-phase workflow is designed for feature branches to ensure history hygiene without risking data loss.