Hi HN,<p>I’m Aloke, one of the co-creators of commands.dev (<a href="https://www.commands.dev/" rel="nofollow">https://www.commands.dev/</a>) and an engineer at Warp (<a href="https://www.warp.dev/" rel="nofollow">https://www.warp.dev/</a>).<p>Commands.dev is a curated, open-source collection of popular terminal commands that lets you quickly search for hard-to-remember terminal commands by title, tag, and description. Each of these pages are also indexed by Google to provide a consistent, well-formatted alternative to the variety of sources these commands turn up now, like StackOverflow.<p>As an engineer who uses the terminal frequently, I often have trouble remembering the exact command I want to execute if it’s not easily searchable within my terminal. Some commands that I run infrequently don’t match up with the underlying task they perform, which makes it even harder to find. For example, to undo my last git commit, I have to search for “git reset”, which I never remember because I’m always thinking “undo”ing my last commit instead of “reset”ing.<p>We built commands.dev so that there would be a centralized place to quickly find and search commands based on their name, description, or category. If you are a Warp user, these commands are also integrated directly into Warp as a feature we call Workflows (<a href="https://docs.warp.dev/features/workflows" rel="nofollow">https://docs.warp.dev/features/workflows</a>) so that you can quickly search and execute them directly from the terminal.<p>These commands are open-source (<a href="https://github.com/warpdotdev/workflows" rel="nofollow">https://github.com/warpdotdev/workflows</a>) and we would love contributions to make commands.dev even more useful. So far, we’ve already had 85 commands created by 22 unique contributors.<p>I’m excited to hear what you think of commands.dev! Our team sincerely hopes this will become a go-to tool on the Internet to consult when developers need to remember a difficult command, either directly on the site or by discovering a commands.dev page when searching Google for help with a command.<p>If you’re interested, join Warp’s Discord (www.warp.dev/discord) and follow us on Twitter (www.twitter.com/warpdotdev).
A couple of things: that I would love to see in commands.dev<p>+ a graph showing what its input and output to that command or command+option<p>+ data type (netdev, IPC, file, pipe) and its data format/schema (INI, CSV, PNG, PEM, text)<p>+ privilege required (file perms, capabilities, security context)<p>+ file naming convention of input/output
Reminds me of tldr, which has been an invaluable tool to find common usages for command line programs. It's particularly great because I have direct access to it in my terminal. It's mostly replaced man pages for my uses.