git-master

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

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/lpjhelder/kronon-forge --skill git-master-lpjhelder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/git-master
Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill git-master-lpjhelder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many developers struggle with creating clean, atomic Git commits, performing interactive rebases, and maintaining a tidy history, leading to confusing repositories and difficult rollbacks.

Core Features & Use Cases

  • Atomic Commit Generation: Enforces conventional commit formats for clear history.
  • Interactive Rebasing: Guides through rebase steps to rewrite commits safely.
  • Branch Management: Assists in creating, switching, and cleaning branches.
  • History Cleanup: Detects and removes redundant or noisy entries.
  • Style Detection: Analyzes existing repo history to suggest appropriate commit styles.

Use case example: When preparing a feature branch for merge, the skill can reformat commits, rebase onto the main branch, and prune irrelevant history automatically.

Quick Start

Ask the git-master skill to rebase the current branch onto main while squashing commits into a single conventional commit.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I perform an interactive rebase to squash commits into a conventional format?

To squash commits during an interactive rebase, the skill guides you through standard git CLI rebase steps to safely rewrite commit history and enforce conventional commit formatting for a clean, atomic branch log.

What is an atomic Git commit and when do I need it for repository maintenance?

An atomic Git commit encapsulates a single, self-contained logical change. You need it during repository maintenance to ensure a tidy history, simplifying conflict resolution and enabling safe rollbacks when preparing a feature branch for merge.

How do I clean up noisy Git history and remove redundant commits before a merge?

To clean up noisy Git history, the skill analyzes your existing repository log to detect and remove redundant entries, automatically pruning irrelevant commits and reformatting messages to match your project's detected style.

Can I use standard git CLI commands to manage branches without installing extra dependencies?

Yes, you can manage branches directly on your local repository using standard git CLI commands without extra dependencies, as the skill operates natively to assist with creating, switching, and cleaning up local branches.

What's the best way to reformat existing Git commits to follow conventional commit standards?

The best way to reformat existing commits is to use the skill's style detection to analyze your repository history, then perform an interactive rebase to rewrite commit messages into appropriate conventional commit formats automatically.

Why does my Git branch history become confusing and difficult to rollback after multiple commits?

Your Git branch history becomes confusing due to non-atomic commits and lack of conventional formatting, making rollbacks difficult; the skill resolves this by enforcing clean commit structures and performing interactive history cleanup.