skills.rest
gjkeller
gjkellerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-master

Manage Git operations with atomic commits, history rewriting, and advanced searching.

2|Updated Jan 20, 2026
Search Tags:#git#code review#version control#commit#history#rebase
One-click install
npx skills add https://github.com/gjkeller/doctor-ralph --skill git-master-gjkeller
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/gjkeller/doctor-ralph/tree/main/inspiration/code-yeongyu-oh-my-opencode/src/features/builtin-skills/git-master
Command: npx skills add https://github.com/gjkeller/doctor-ralph --skill git-master-gjkeller

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines Git operations by enforcing atomic commits, managing complex history rewrites, and enabling efficient searching of past changes, ensuring a clean and understandable project history.

Core Features & Use Cases

  • Atomic Commits: Enforces the creation of small, focused commits, making code reviews easier and rollbacks safer.
  • History Rewriting: Handles rebasing, squashing, and cleaning up commit history to maintain a linear and logical progression.
  • History Search: Allows users to find specific changes, identify when a feature was introduced, or determine who wrote a particular piece of code using tools like git blame and git bisect.
  • Use Case: Before merging a large feature, use this Skill to break down your work into atomic commits, rebase cleanly onto the main branch, and then efficiently search the history to understand the impact of specific changes.

Quick Start

Use the git-master skill to commit your staged changes with atomic 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 in git for safer rollbacks?▼

To enforce atomic commits in Git, you create small, focused commits that group related changes together. This practice makes code reviews easier and ensures safer rollbacks by keeping your project history clean.

What is the best way to rebase and squash a messy git history before merging?▼

The best way to rebase and squash a messy Git history is to rewrite your commits to form a linear and logical progression. This cleans up your commit history before merging a large feature into the main branch.

How does git bisect help with finding when a specific change was introduced?▼

Git bisect helps find when a specific change was introduced by efficiently searching past changes. It identifies the exact commit that introduced a feature or bug, allowing you to understand the impact of specific modifications.

Can I use git blame to determine who wrote a particular piece of code?▼

Yes, you can use Git blame to determine who wrote a particular piece of code. It enables efficient history searching by mapping specific lines back to their originating commit and author.

Why should I break down work into atomic commits before merging a feature?▼

You should break down work into atomic commits before merging a feature to maintain a clean and understandable project history. Atomic commits enforce dependency ordering and make complex conflict resolution across various Git modes manageable.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
WesleyMFrederickWesleyMFrederick

merging-feature-branches-to-main

Squashes Git feature-branch history into a single commit when merging to main.

Community
Basic
liumeixinliumeixin
4

requesting-code-review

Automate code review with static analysis and an independent reviewer subagent.

Community
Advanced
markus41markus41
1

gitworfkflows

Manage Git branching, commits, rebasing, and pull requests.

Community
Basic