skills.rest
naps62
naps62COMMUNITY
Explore all skills by this author →
Website𝕏@naps62GitHub

git-master

Automate Git operations with atomic commits, rebase/squash strategies, and history search.

1|Updated Oct 5, 2024
Search Tags:#git#rebase#atomic-commits#version-control#blame#history-search
One-click install
npx skills add https://github.com/naps62/nixos-config --skill git-master-naps62
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/naps62/nixos-config/tree/main/home/common/programs/opencode/skills/git-master
Command: npx skills add https://github.com/naps62/nixos-config --skill git-master-naps62

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows often drift into messy histories and error-prone merges. This skill enforces atomic commits, provides guided rebase/squash strategies, and enables precise history searches (blame, bisect, log -S) to improve traceability and maintainability.

Core Features & Use Cases

  • Atomic commits by default for multi-file changes to ensure clear boundaries and easier reversions.
  • Rebase surgery and history archaeology to rewrite history cleanly, prune conflicts, and locate when changes were introduced.
  • Use cases include preparing feature branches for PRs with deterministic commit grouping, tracing changes with blame/bisect, and quick history searches across the repository.

Quick Start

Run the Git Master Agent to begin applying atomic commits and history queries on your current branch.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I keep my git history clean with atomic commits?▼

Atomic commits ensure multi-file changes are grouped logically to create clear boundaries and easier reversions. This approach enforces disciplined branch-based workflows to maintain repository traceability and prevent messy git histories.

What is the best way to squash and rebase feature branches before a PR?▼

Rebase surgery and squash strategies rewrite history cleanly to group commits deterministically. This prepares feature branches for PRs by pruning conflicts and ensuring reproducible commit grouping across multi-file changes.

How does git bisect and blame work for tracing changes?▼

Git bisect and blame enable precise history archaeology to locate exactly when and where changes were introduced. This traceability is critical for branch-based workflows tracking multi-file commits across repository history.

Can I use scripted tasks to automate reproducible git workflows?▼

Scripted tasks automate git operations to ensure deterministic, reproducible results. This requires disciplined usage and support for scripted execution to maintain atomic commits and clean history across branch-based workflows.

Why do my merge workflows drift into error-prone and messy histories?▼

Merge workflows without atomic commits often drift into messy histories and error-prone merges. Enforcing atomic commits with guided rebase strategies prevents this drift and maintains clear change boundaries for easier reversions.

Related Skills

Explore More Software Engineering Skills→
realsigridjinrealsigridjin
20

git-master

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

Community
Intermediate
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced
bikeindexbikeindex
308

merge-conflicts

Guide git merge conflict resolution with merge instead of rebase.

Official
Intermediate