git-master

Plan and execute atomic Git commits with test pairing and dependency-aware ordering.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/frankxai/arcanea-opencode --skill git-master-frankxai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/frankxai/arcanea-opencode/tree/main/src/features/builtin-skills/git-master
Command: npx skills add https://github.com/frankxai/arcanea-opencode --skill git-master-frankxai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers automate the creation of atomic, well-structured Git commits and manage history with rebases and searches.

Core Features & Use Cases

  • Atomic commits and structured history
  • Rebase/squash automation with safety checks
  • History search and diagnostics (blame, log -S, bisect)

Quick Start

Plan and execute atomic commits for the active branch, splitting changes by directory and pairing tests.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I split multi-file changes into atomic git commits?

To create atomic git commits, this Skill groups multi-file changes by directory and dependency ordering, pairing source files with their corresponding tests to produce clean, review-friendly commit history.

What's the best way to squash and rebase git history safely?

Squashing and rebasing git history safely requires automated safety checks. This Skill executes rebases with structured validations to prevent broken history, ensuring your branch remains clean and recoverable during interactive rewrites.

When do I need atomic commits before merging a feature branch?

You need atomic commits before merging when preparing clean, review-friendly history for pull requests. This Skill enforces multi-file grouping, test pairing, and dependency-aware ordering to make feature work, bug fixes, and refactors easier to review.

Can I search git history for specific changes using blame and bisect?

Yes, you can search git history using blame, log -S, and bisect diagnostics. This Skill automates history searches to help identify when specific changes were introduced and locate the exact commits responsible for regressions.

Why does my git branch have messy history before a pull request?

Messy git branch history before a pull request happens when changes are committed arbitrarily without atomic scoping. This Skill fixes it by planning dependency-aware commit ordering and generating clear commit messages for each logical change.