One dense page of the things people look up again and again, grouped by task and quick to search.
Nobody reads a cheat sheet. They glance at it forty times, usually mid-task with something half broken. This one covers everyday Git for new starters at a made-up software company: 46 commands and a filter box. It's for looking things up on screen, and it has no print layout. Use it as a pattern for your own tool, whether that's a spreadsheet, a till system or a command line.
Who it's for
Whoever on the team knows the tool best, writing for the people who started this month. It also suits a trainer who wants one page to leave behind after a workshop.
A cheat sheet reminds people of things they've been shown once. It can't teach the tool from nothing, so pair it with a walkthrough. Past fifty or so entries, it has turned into a manual.
What a good one contains
- Groups named for the task. "Undo", "Sync with the remote", "When a merge or rebase conflicts". A beginner knows what they want to do long before they know what the command is called.
- One line per entry, in plain words.
git stash "shelves uncommitted changes to tracked files and gives you a clean working tree". An entry that needs a paragraph belongs in the docs.
- Only what's used most weeks. The sample stops at 46. Leaving things out is the work, because every rare flag you add makes the common ones slower to find.
- A filter that matches everyday words. "who changed" finds
git blame, because each row carries a few search words that aren't shown.
- Tags on what destroys work. Four entries have a small rust-colored tag, such as "uncommitted work is gone for good" on
git reset --hard HEAD~1.
- House rules. Four lines on how this team does it: branch names, when to rebase, where to ask. No public cheat sheet has that part.
- A date and an owner. "Rev. 2026-11-09" and a name tell readers whether to trust it and who to tell when it's wrong.
Run every line yourself
A wrong command on a cheat sheet gets pasted into a terminal by someone who can't tell it's wrong. Run each one in a scratch copy, on the version your team has installed, and read each explanation against what happened. The sample says it needs Git 2.23 or newer, because git switch and git restore don't exist before that.
It goes stale quietly. When the team changes a habit, a new branch name or a different way to merge, change the page that day, in the conversation where you made it, and bump the date. People who bookmarked the link get the new version without being told.
How to send it
As an open link. It's reference material, and a good one gets passed to the next new starter. Add a password only if yours names internal servers or customers.
Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.