Best command-line cheat sheet tools
Compare tldr, cheat, and navi for command examples, project notes, and executable snippets.
Updated
short verdict
Use tldr for shared examples, cheat for personal and project notes, or navi for a searchable menu of executable snippets.
A command reference can be a page you read, a note you maintain, or a snippet you run. Decide who owns the examples and how they reach your shell.
this page is for
- short community-maintained command examples
- personal and project-specific command notes
- searchable and executable command snippets
Use tldr for concise examples of common command options across operating systems.
best for
- short community-maintained command examples
strengths
- Read practical command examples through a choice of clients
- Choose translated pages contributed by the community
- Contribute Markdown pages through the shared repository
weaknesses
- Example pages are deliberately concise; check full command documentation for exhaustive option details.
Use cheat to maintain plain-text command notes with tags and directory-scoped sheets.
best for
- personal and project-specific command notes
strengths
- Separate read-only community sheets from writable personal cheatpaths
- Search text or regular expressions and filter by tags
- Discover .cheat directories in the current directory or its ancestors
weaknesses
- Personal and project sheets need maintenance as your commands and conventions change.
Use navi to search a command menu, fill argument choices, and run a selected snippet.
best for
- searchable and executable command snippets
strengths
- Browse fuzzy-searchable menus of snippets
- Define parameter choices and variable substitution in .cheat files
- Use standalone or shell-widget modes with community or private sheets
weaknesses
- Sheets can execute commands to supply arguments or run a snippet; review imported sheets before using them.
How to choose
- Choose tldr for concise community examples across operating systems.
- Choose cheat for tagged personal notes and project-scoped .cheat directories.
- Choose navi for a fuzzy menu with parameter choices and shell-widget integration.
- Review executable snippets and argument-producing commands before importing new sheets.
FAQ
- Should I use a cheat sheet as the complete command reference?
- Treat a sheet as a starting point for a familiar task. Check the command documentation when an option, version, or side effect is unclear.
- How do I keep project commands separate from shared examples?
- cheat supports multiple cheatpaths, including read-only community paths and writable personal paths. It also discovers .cheat directories in a project’s current directory or ancestors, so project notes can follow your working directory.