git-master

Name: git-master
Availability: InStock
Author: Sammykins

Enforce atomic commits, controlled rebases, and precise history searches.

Updated Oct 31, 2024

Search Tags:#git #bisect #atomic-commits #version-control #blame #rebasing #history-search

Ready to run

npx skills add https://github.com/thesammykins/dotfiles --skill git-master-thesammykins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/thesammykins/dotfiles/tree/main/.agents/skills/git-master
Command: npx skills add https://github.com/thesammykins/dotfiles --skill git-master-thesammykins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures disciplined Git workflows by enforcing atomic commits, reliable rebases, and efficient history searches, reducing mistakes and drift in collaborative development.

Core Features & Use Cases

Atomic commits: enforce small, focused commits that isolate changes.
Rebase/Squash guidance: optimize history through safe rebases and meaningful squashes.
History exploration: powerful search with blame, bisect, and -S/-G style queries for traceability.
Team workflows: broadcasts prompts and checks to align contributors on consistent practices.

Quick Start

Ask the agent to guide your current repository through an atomic-commit driven workflow with history-search prompts for precise tracing.

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 to keep my history clean?▼

Git bisect uses binary search to pinpoint the exact commit that introduced a bug. This workflow guides you through the bisect process alongside blame and -S/-G style queries, enabling precise history searches for full traceability across your repository.

What's the best way to rebase and squash commits without losing changes?▼

Git blame identifies who wrote specific lines of code and when they were added. This workflow leverages blame alongside history search prompts like "who wrote" and "when was X added" to drive precise tracing across your repository.

How do I find which commit introduced a specific bug using Git bisect?▼

Can I use Git blame to find who wrote specific lines of code?▼

How do I perform a safe Git rebase and squash for my feature branch?▼

Controlled rebases and meaningful squashes optimize your Git history safely. This workflow provides rebase and squash guidance to help you consolidate related commits while protecting your changes from common interactive rebase mistakes.