Git isn't hard once you build a few good habits early. Here's the short list that covers almost everything.
New developers usually get taught git backwards — starting with rebasing, cherry-picking, and reflog before they've even built the habit of committing properly. Here's the order that actually matters, starting with the stuff you'll use every single day.
A commit that changes 40 files across three features is nearly impossible to review or revert cleanly. Commit when you finish a coherent chunk of work, not just at the end of the day. Future you (or whoever's debugging six months from now) will thank you.
The diff already shows what changed. "Fixed bug" tells nobody anything. "ABC-204: null check was missing on refund amount" tells a story someone can use later when they're trying to understand why a line exists.
A branch that lives for three weeks drifts further and further from main, and the eventual merge becomes painful. Smaller tickets, smaller branches, merged faster — everyone's life gets easier.
Branching off an outdated main is one of the most common sources of annoying merge conflicts later. It takes two seconds to pull first.
Nothing half-finished should sit on main. If it's not ready, it stays on a branch or behind a flag.
None of these habits require a tool, they're just discipline. But the typing part — checking out main, pulling, branching with the right name, committing with the ticket reference — is exactly the repetitive part that's easy to skip when you're in a rush. That's what jitly start ABC-123 and jitly done take care of, so the good habit happens automatically instead of depending on you remembering it every time.