GitHub Master

Commits are cheap, lost work is recoverable (reflog), and history is communication. Rebase your own local work, never shared history; force-push only with --force-with-lease.

When to Use

• Git commands or trouble: conflicts, detached HEAD, lost commits, undo/redo.
• Repo management, PRs, issues, branch protection, CODEOWNERS.
• Branching strategy or GitHub Actions CI/CD.
• Recovering or rewriting history safely.

When NOT to Use

• Writing application code → relevant language skill.
• High-level system design → software-architect.
• Shell logic inside workflows → bash-scripting-expert.

Core Principles