skills.rest
GDSDN
GDSDNCOMMUNITY
Explore all skills by this author →
GitHub

git-master

Manages Git commits, rebases, and searches with atomicity and style enforcement.

3|Updated Feb 7, 2026
Search Tags:#git#code review#version control#commit#history#rebase
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill git-master-gdsdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/utilities/git-master
Command: npx skills add https://github.com/GDSDN/kord-aios --skill git-master-gdsdn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures your Git commit history is clean, atomic, and understandable, preventing messy commits and making it easier to track changes and revert issues.

Core Features & Use Cases

  • Atomic Commits: Enforces the creation of multiple, focused commits for changes, rather than large, monolithic ones.
  • History Management: Supports rebase, squash, and finding specific changes using tools like git blame and git bisect.
  • Use Case: When making several unrelated changes, this Skill will guide you to create separate, logical commits for each change, making your pull requests clearer and easier to review.

Quick Start

Use the git-master skill to commit your staged changes following best practices.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I enforce atomic commits when I have multiple unrelated changes staged in Git?▼

To enforce atomic commits, this Skill analyzes your staged changes and guides you to split them into multiple focused, logical commits. This prevents monolithic commits and ensures your Git history remains clean, understandable, and easy to review.

What is the best way to clean up a messy Git commit history before a pull request?▼

The best way to clean up messy Git commit history is by using rebase and squash operations. This Skill supports history rewriting to combine related commits and enforce commit style best practices, resulting in a clearer and more maintainable branch history.

How does Git blame or bisect help find specific changes in my version control history?▼

Git blame and bisect help find specific changes by tracking when a line was modified or locating the commit that introduced a bug. This Skill integrates these history searching modes to perform detailed change analysis and isolate issues in your codebase.

Can I use this Skill to manage branch rebasing and commit style detection automatically?▼

Yes, you can use this Skill to manage branch rebasing and commit style detection. It supports dedicated modes for committing and rebasing, automatically enforcing best practices for commit atomicity and branch management to maintain a clean history.

Why should I split large commits into atomic commits for code review?▼

You should split large commits into atomic commits because it makes tracking changes and reverting issues significantly easier. This Skill ensures your commit history is clean and understandable, which directly improves the clarity and speed of pull request reviews.

Related Skills

Explore More Software Engineering Skills→
jeremy-newhousejeremy-newhouse

wa:dev-branch

Create or switch to a feature branch with enforced naming conventions.

Community
Intermediate
wewetv1987-cellwewetv1987-cell

git-helper

Manage Git repository status, pull, push, branch, and log operations.

Community
Basic
massgenmassgen
1.1k

pr-checks

Automate PR checks with pre-commit hooks, tests, and CodeRabbit feedback.

Official
Advanced
maggitmaggit

rebase

Plan and execute non-interactive git rebase operations with safety checks.

Community
Intermediate