skills.rest
BOHUYESHAN-APB
BOHUYESHAN-APBCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-master

Enforce atomic commits, controlled rebases, and precise Git history queries.

2|Updated Apr 30, 2026
Search Tags:#git#commits#rebase#squash#bisect#version-control#blame
One-click install
npx skills add https://github.com/BOHUYESHAN-APB/openagent-labforge-bio --skill git-master-bohuyeshan-apb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/BOHUYESHAN-APB/openagent-labforge-bio/tree/main/src/skills/git-master
Command: npx skills add https://github.com/BOHUYESHAN-APB/openagent-labforge-bio --skill git-master-bohuyeshan-apb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows often suffer from non-atomic commits, scattered history, and risky rebases. Git Master enforces atomic commits, controlled rebase/squash, and precise history searches (blame, bisect, log -S) to keep projects auditable and changes traceable.

Core Features & Use Cases

  • Atomic commits by default: split changes into small, reviewable units aligned with features or fixes.
  • History-centric operations: robust support for blame, log, diff, bisect, and rebase workflows.
  • Deterministic task guidance: load skills deterministically and ensure safe manipulations of commit history in complex repos.

Quick Start

Ask Git Master to organize a feature change into atomic commits with an explicit history plan.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I organize a feature change into atomic commits in git?▼

To perform a git bisect, you automate rigorous history queries to find the exact commit that introduced a bug. Git bisect uses binary search across your commit history, pairing with blame and log -S to keep changes traceable in large codebases.

What is the best way to perform a git rebase and squash safely?▼

Git blame enforces precise history searches to keep projects auditable and changes traceable. By automating rigorous history queries, blame identifies exactly which commit and author last modified each line, resolving non-atomic commit issues across large codebases.

Can I use automated git workflows for complex repos with multiple branches?▼

Yes, automated git workflows fit complex repos with multiple branches. They enforce atomic commits, disciplined rebases, and precise history queries like blame, bisect, and log -S, ensuring safe manipulations of commit history across large codebases.

Why do scattered git commits make version control difficult to audit?▼

Scattered git commits make version control difficult to audit because they group unrelated changes, obscuring feature boundaries. Enforcing atomic commits splits changes into small, reviewable units, ensuring rigorous history queries and precise traceability across branches.

Related Skills

Explore More Software Engineering Skills→
TienchingTienching
3

git-master

Route and execute advanced Git tasks like atomic commits, rebasing, and history cleanup.

Community
Intermediate
ThomashighbaughThomashighbaugh
1

changelog-generator

Generate structured Markdown release notes from categorized git commit histories.

Community
Intermediate
dtbuchholzdtbuchholz

commit-push-pr

Stage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.

Community
Intermediate
fullykubedfullykubed
2

Git

Automate Git commits, rebases, and squashes with safety prompts.

Community
Advanced