skills.rest
KYRIE66nb
KYRIE66nbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-master

Perform atomic commits, interactive rebases, and branch history cleanup.

Updated Apr 8, 2026
Search Tags:#git#commit#code collaboration#branch-management#version-control#rebasing#history-cleanup
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill git-master-kyrie66nb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/git-master
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill git-master-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow fragmentation is solved by enabling atomic commits, safe rebasing, and streamlined branch handling.

Core Features & Use Cases

  • Atomic commits with conventional format
  • Interactive rebasing
  • Branch management
  • History cleanup
  • Style detection from repo history

Quick Start

Invoke the git-master agent to perform atomic commits, interactive rebases, and branch history cleanup.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I make atomic git commits with a conventional format?▼

Atomic git commits are generated by invoking the agent to route changes into structured, conventional-commit style messages, ensuring deterministic commit history for multi-contributor projects.

What is the best way to clean up a fragmented git branch history?▼

Branch history cleanup is achieved through scripted interactive rebasing, which restructures commits deterministically to maintain a predictable and clean branch management workflow.

Can I use interactive rebasing for branch management on multi-contributor repositories?▼

Interactive rebasing is supported for multi-contributor repositories, applying scripted routing to enforce branch hygiene and structured history cleanup across shared project branches.

How does style detection from repo history work for git commits?▼

Style detection analyzes existing repository history to infer commit conventions, automatically applying those patterns to enforce consistent conventional-commit formatting during atomic commit generation.

When do I need to rebase git history instead of merging branches?▼

Rebasing git history is needed when you require a deterministic, linear project timeline, using history cleanup to avoid merge clutter and maintain strict branch hygiene for multiple contributors.

Related Skills

Explore More Software Engineering Skills→
Geralt1983Geralt1983
1

git-sync

Commit and push local workspace changes to a remote GitHub repository.

Community
Basic
RooseveltAdvisorsRooseveltAdvisors
1

DevFlow

Detect the current development stage and enforce CI/CD pipeline adherence.

Community
Advanced
hivellmhivellm
15

rulebook-git-workflow

Enforce branch naming, conventional commits, and PR guidelines in Git workflows.

Official
Basic
lpjhelderlpjhelder

git-master

Create atomic Git commits with conventional formatting and manage repository history.

Community
Intermediate