HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
denisidoro
navi
Rust2019–2026
denisidoro / navi

navi

An interactive cheatsheet tool for the command-line

19Distinct people
22Mentions
0Explicit recommenders
17.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An interactive cheatsheet tool for the command-line

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year22 dated mentions

Observed mentions: 2019-09-20 22:56:27 UTC to 2026-04-08 15:19:59 UTC.

024682019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC817
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

22 sources
I swear I want this as a general tool for all command-line tools. Start the tool, and just list all of the options in order of usage popularity to toggle on as desired, with a brief explanation, and a field to paste in arguments like filenames or values when needed. If an option is commonly used with another (or requires it), provide those hints (or automatically add the necessary values). If a value itself has structure (e.g. is itself a shell command), drill down recursively. Ensure that quotes and spaces and special characters always get escaped correctly. In other words, a general-purpose command-line builder. And while we're at it, be able to save particular "templates" for fast re-use, identifying which values should be editable in the future. I can't be the first person to think of this, but I've never come across anything like it
Read the rest
and don't understand why not. It doesn't require AI or anything. Maybe it's the difficulty involved in creating the metadata for each tool, since man pages aren't machine-readable. But maybe that's where AI can help -- not in the tool itself, but to create the initial database of tool options, that can then be maintained by hand? (Navi [1] does the templating part, but not the "interactive builder" part.) [1] https://github.com/denisidoro/navi
In Show HN: Ez FFmpeg – Video editing in plain English
I see no benefits in using Warp over a regular (and more supported) GPU-accelerated terminal emulator. It's just "prettier" out of the box, and it seems to market quite a bit to people that either don't know how to configure their shells, or don't know what they're doing. - If you want fuzzy command, history, file / contents search, use fzf [0] (you should probably be using fzf and ripgrep [1] anyway if you work daily in your terminal). - If you want sessions, use a multiplexer like tmux [2] or zellij [3]. - If you need to have your own "cheatsheets" use navi [4]. If you want to sync them with your team, use whatever sync solution you like. - If you think you need a text editor in your shell's command line, reconsider. If you *really* want to edit and re-execute the last command in your editor of choice, use something like "fc $!
Read the rest
" [5] or create your own shell solution for it. - If you want a sexy prompt use starship [6]. - If you want terminal sharing use tty-share [7]. - If you want to ask GPT for help, don't do it in your terminal. Open up ChatGPT (or whatever future UI will exist), ask your question, and check that there's nothing harmful in what your about to execute. Sometimes friction is good. For each of these ^ pieces of software there are tens and hundreds of alternatives. If you want a terminal that's pretty out-of-the-box, where things are "clickable", you don't have the time or interest to invest your energy in learning tools that could massively boost your productivity for years to come, and you don't care about designing your own workflow and being able swap parts of it at any point, without depending on any single "app", and if you don't mind "logging into your terminal" (what the actual fuck, excuse the language) or the terminal adding its own SSH wrapper and doing things you don't know to the hosts you connect, then maybe Warp is OK for you. But then again, maybe you're not going in the right direction. There are so many more awesome ways you could improve your shell experience than making things clicky. I don't understand what the market is for Warp, is it for wanna-be professionals that can't be bothered to become professionals? I completely fail to see how this could succeed as a paid product, especially with a subscription model. [0] https://github.com/junegunn/fzf [1] https://github.com/BurntSushi/ripgrep [2] https://github.com/tmux/tmux [3] https://github.com/zellij-org/zellij [4] https://github.com/denisidoro/navi [5] https://shapeshed.com/unix-fc [6] https://starship.rs/ [7] https://github.com/elisescu/tty-share
In Telemetry is now optional in Warp
I use navi: https://github.com/denisidoro/navi > navi allows you to browse through cheatsheets (that you may write yourself or download from maintainers) and execute commands. Suggested values for arguments are dynamically displayed in a list. It also lets you use cheatsheets from tldr and cheat.sh from it (besides your own cheatsheets). I've started to mostly just maintain my own, copying what I find most useful from those repositories, though.
In Ask HN: Can I see your cheatsheet?

Showing the 15 most recent of 22 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.