smith-git

Enforce safe Git workflows for commits, merges, and rebases.

1|Updated Nov 25, 2025

Search Tags:#git #workflow #commit #branching #rebase #gpg-signing

Ready to run

npx skills add https://github.com/tianjianjiang/smith --skill smith-git

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smith-git
Source: https://github.com/tianjianjiang/smith/tree/main/smith-git
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow gotchas and non-obvious practices can lead to messy history and risky operations; this skill teaches safe, disciplined Git habits to keep commits, branches, and merges clean.

Core Features & Use Cases

Atomic commits: Each change is isolated, making history easy to review and revert.
GPG signing: All commits are cryptographically signed for provenance and trust.
Linear history: Guidance to minimize unnecessary merge commits and preserve a clean history.
Branching discipline: Clear rules for feature, release, and hotfix branches, and safe merge/rebase flows.

Quick Start

Apply this skill to enforce a safe, linear Git workflow during commits, merges, and rebases.

Frequently Asked Questions about smith-git

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

FAQPage Schema

How do I keep my git history linear and avoid messy merge commits?▼

Git workflow rules for safe commits require isolating each change into atomic commits, using git mv for renames, and GPG signing all commits. This makes history easy to review and revert while ensuring cryptographic provenance and trust.

What is the best way to structure feature, release, and hotfix branches?▼

The best way to structure branches is by applying strict branching discipline with clear rules for feature, release, and hotfix branches. This ensures safe merge and rebase flows while maintaining a clean, linear history across your repositories.

Do I need GPG signing for every commit in a shared repository?▼

Yes, GPG signing for every commit is required to ensure provenance and trust. Cryptographically signing commits enforces safe Git workflows and verifies authorship across both personal and shared repositories.

Why should I use git mv for file renames instead of standard shell commands?▼

You should use git mv for file renames because it is a mandatory rule in safe Git workflows. This practice preserves the file history accurately and prevents non-obvious gotchas that can lead to messy repository history.

How do I enforce safe push and pull request practices in my Git workflow?▼

You can enforce safe push and PR practices by applying strict workflow rules that mandate atomic commits, linear history, and branching discipline. This guidance ensures safe merges, rebases, and PR workflows across your repositories.