git-master

Name: git-master
Availability: InStock
Author: openEuler

Generate atomic Git commits and rebase history with forensic search.

3|2|Updated Apr 24, 2026

Search Tags:#git #debugging #version control #commit #code history #rebase

Ready to run

npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill git-master-openeuler-mirror

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/src/opencode/features/builtin-skills/git-master
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill git-master-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common issue of messy, non-atomic Git history by enforcing structured commit practices, automated history cleanup, and precise search capabilities.

Core Features & Use Cases

Commit Architect: Automatically enforces atomic commits by splitting large changes into logical, manageable units based on directory and concern.
Rebase Surgeon: Safely cleans up local history through interactive rebasing, autosquash, and conflict resolution.
History Archaeologist: Quickly identifies when specific code was introduced, who wrote it, or when a bug was first injected using advanced log analysis and bisecting.

Quick Start

Use the git-master skill to analyze my current changes and create atomic commits following the repository's established style.

Frequently Asked Questions about git-master

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

FAQPage Schema

How do I split large staged changes into atomic commits based on directory and concern?▼

To create atomic commits, the Skill analyzes your current changes and splits them into logical, manageable units based on directory and concern. It enforces structured commit practices to ensure a clean history.

What is the best way to clean up messy local Git history before pushing?▼

Cleaning up local Git history is handled through interactive rebasing, autosquash, and conflict resolution. This safely rewrites your branch to ensure a clean and structured commit sequence.

How do I find when a specific bug was first injected into the code history?▼

To find when a bug was injected into the code history, the Skill performs forensic code search using advanced log analysis and bisecting. This precisely identifies when the code was introduced and who wrote it.

Can I automate interactive rebasing and conflict resolution for my branch?▼

Interactive rebasing and conflict resolution can be automated to safely clean up local history. The Skill applies these operations to satisfy requirements for semantic versioning and dependency-ordered commits.

Why do I need atomic commits for dependency-ordered version control?▼

Atomic commits are required for dependency-ordered version control because they isolate logical changes into manageable units. This precise attribution of code changes ensures a clean, semantic commit history.