git-master

Perform atomic commits, controlled rebases, and precise git history searches.

Updated Feb 15, 2026

Search Tags:#git #workflow #bisect #atomic-commits #blame #rebases #history-search

Ready to run

npx skills add https://github.com/zhangjunxiangg/Zeus_OS --skill git-master-zhangjunxiangg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/zhangjunxiangg/Zeus_OS/tree/main/src/features/builtin-skills/git-master
Command: npx skills add https://github.com/zhangjunxiangg/Zeus_OS --skill git-master-zhangjunxiangg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows can become error-prone and hard to audit without disciplined commits and clear history operations; this skill provides a structured approach to atomic commits, safe rebases/squashes, and targeted history queries to keep a pristine project history.

Core Features & Use Cases

Atomic commits: enforce single-purpose commits that are easy to review and revert.
Controlled rebases & squashes: plan and execute history rewrites without breaking dependencies.
History search & blame: locate when and where changes were introduced across branches and files.
Use case: debugging across multiple commits to identify the exact change introducing a bug.

Quick Start

Ask the agent to perform a git operation on your current branch, such as creating atomic commits during a feature-development workflow.

Frequently Asked Questions about git-master

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

FAQPage Schema

How do I create atomic commits to keep my git history clean?▼

Atomic commits enforce single-purpose, explicit grouping rules so each commit is easy to review and revert, maintaining a pristine git history without mixing unrelated changes together.

What is the best way to execute controlled rebases and squashes without breaking dependencies?▼

Controlled rebases and squashes require planning history rewrites before execution, ensuring structural integrity and preventing broken dependencies across branches during your git workflow operations.

How does git bisect help locate the exact commit introducing a bug across multiple commits?▼

Git bisect combined with precise history search and blame locates exactly when and where changes were introduced across branches and files, tracing lineage to identify the specific commit introducing a bug.

Can I use this git workflow for fast lineage tracing across multiple branches?▼

Yes, you can use this structured git workflow for fast lineage tracing across branches, targeting software teams needing reliable commit hygiene, deterministic rebases, and clear history searches.

When should I avoid rebases and history rewrites in my git workflow?▼

You should avoid rebases and history rewrites when explicit grouping rules cannot be enforced or when deterministic dependency tracking is unavailable, preventing uncontrolled history modifications.