# Cheat Sheets — Examples

> Hands-on walkthroughs with the Cheat Sheets: look up a git command, find a sheet, filter commands, copy a snippet, and share it via a deep link.

Source: https://www.jpkc.com/db/en/tools/cheatsheet/examples/

Back to the overview: [Cheat Sheets](https://www.jpkc.com/db/en/tools/cheatsheet/) · Open the tool live: [www.jpkc.com/tools/cheatsheet/](https://www.jpkc.com/tools/cheatsheet/)

The [manual](https://www.jpkc.com/db/en/tools/cheatsheet/manual/) explains every feature in detail. This page adds **concrete workflows** — typical lookup situations, step by step.

## Example 1: Look up a git command fast

The classic — you want to undo a commit and can't remember whether it was `reset` or `revert`.

1. Open the [Cheat Sheets](https://www.jpkc.com/tools/cheatsheet/). The **Git** sheet is already loaded by default.
2. Type a keyword into the `Search` field, e.g. `revert`. The command list filters live, sections with no match disappear, and the counter updates to the number of still-matching commands (format `X / N commands`).
3. Read the matching entry — command, short description, and (often) an example. Click the clipboard icon and the command is on your clipboard.
4. In the terminal, replace the placeholder (e.g. `<commit>` with the real hash) — done.

The keyword doesn't have to be a command name: because the search also runs over the descriptions, you can find the right `git` command via a word like `stash` or `undo` if it appears in the description.

## Example 2: Find the right sheet when you're unsure of the tool name

You want to synchronize files but aren't sure whether the tool is `rsync` or something else.

1. Click the `Cheat Sheet` dropdown at the top. The category-grouped list of all 219 sheets opens.
2. Type a fragment into the search field (`Search cheat sheets…`), e.g. `sync`. The list narrows to matching sheet **names**; categories with no match are hidden.
3. Navigate with **Up/Down arrows** and confirm with **Enter** — or click directly. The sheet loads.

Alternatively, browse the categories: looking for something about backups, you'll find `rsync`, `restic`, `rustic`, `BorgBackup`, `Rclone`, and more side by side under **Remote & Backup** — handy for comparing alternatives.

## Example 3: Search a Docker sheet precisely

You need the syntax to inspect a running container.

1. Pick **Docker** from the `Cheat Sheet` dropdown (or open [`/tools/cheatsheet/#docker`](https://www.jpkc.com/tools/cheatsheet/#docker) directly).
2. Instead of scrolling, type `logs` or `exec` into the `Search` field. The list shows only the matching commands.
3. If you'd rather get an overview of a whole topic block, use the `Section` dropdown and jump straight to the section — the page scrolls there smoothly.
4. Copy the command you want via its clipboard button.

Remember: command search and section jump are two routes to the goal — the search is faster for a known keyword, the `Section` dropdown is better when you want to skim a topic.

## Example 4: Copy a snippet and use it cleanly

You want to take over a ready-made example, not just the bare command.

1. Find the entry (e.g. `ssh-keygen` in the **ssh** sheet).
2. Many entries have their own syntax-highlighted **example block** below the description with a real invocation. Next to it sits a second clipboard button — it copies the **example**, not the generic command line.
3. Paste it in the terminal and just adjust the specific values (path, hostname, file name).

The distinction pays off: the upper button copies the generic syntax with placeholders (`<…>`), while the button on the example copies a filled-in, runnable invocation you only need to tweak.

## Example 5: Share or bookmark a sheet via a deep link

You're explaining something to a colleague and want to send them exactly the right sheet.

1. Pick the sheet (e.g. **nginx**). The address bar now shows `…/tools/cheatsheet/#nginx`.
2. Copy that URL and pass it along — when they open it, your colleague lands straight in the nginx sheet, no searching needed.
3. For sheets you use often, a **bookmark** on the hash link pays off. Next time you jump in with a single click.

Handy: because the hash is set without a new history entry, switching between sheets doesn't clutter your back button.

## Example 6: Skim a new tool instead of reading the man page

You hit `restic` for the first time and want to get a feel for what it does in two minutes.

1. Load the **restic** sheet.
2. Leave the search empty and open the `Section` dropdown — the section titles (e.g. `Repository Initialization`, `Creating Backups`, `Listing Snapshots`, `Restoring Data`) are a mini table of contents for the topic.
3. Jump through the sections in order. You see the typical steps in their logical sequence — more compact than any man page, but with real examples.

That's where the sheets shine for learning: they show not *every* option but the ones you actually need day to day — in a structure you take in at a glance.

---

Going deeper: the [manual](https://www.jpkc.com/db/en/tools/cheatsheet/manual/) for every feature and the data structure, the [tips & tricks](https://www.jpkc.com/db/en/tools/cheatsheet/tips/) for knacks and pitfalls. You can try all of it right in the [tool](https://www.jpkc.com/tools/cheatsheet/).