SaaSHub helps you find the best software and product alternatives Learn more →
Cli-guidelines Alternatives
Similar projects and alternatives to cli-guidelines
-
-
InfluxDB
InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
-
-
-
-
-
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
-
-
picocli
Picocli is a modern framework for building powerful, user-friendly, GraalVM-enabled command line apps with ease. It supports colors, autocompletion, subcommands, and more. In 1 source file so apps can include as source & avoid adding a dependency. Written in Java, usable from Groovy, Kotlin, Scala, etc.
-
-
-
argparse-benchmarks-rs
Discontinued Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better cli-guidelines alternative or higher similarity.
cli-guidelines discussion
cli-guidelines reviews and mentions
Posts with mentions or reviews of cli-guidelines.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-04-24.
- Como criar uma CLI com React
-
🥳 We built the cli of our dreams to send sms ❣️
This is the source code for the guide. To read it, go to clig.dev.
-
Some Terminal Frustrations
I think I remember swyx had compiled some thoughts on CLIs: https://github.com/swyxio/cli-cheatsheet. I particularly liked this part, where it starts by collecting examples of CLI apps like by the the authors: https://clig.dev/#the-basics.
Beyond that, I am enjoying a little bit too much customizing Fish, bobthefish, FZF, and replacements for established CLI apps (e.g., find/fd). I spend too much time asking Claude how to do various things. And I am the happiest with my current setup—until I have to SSH into the barren lands of a production host.
-
"Rules" that terminal programs follow
In the same category of command line program guidelines: https://clig.dev/
-
I made an ls alternative for my personal use it turned out to be amazing
This is a good, open-source resource for guidelines on creating CLIs, which goes over some common mistakes.
https://clig.dev/
-
Ask HN: What are some command line utilites that have great UX?
I can't think of any cli tools with great UX :( usually the important tools have lots of obtuse commands, and the small neat tools only have a couple trivial options.
But here's some guidelines as you make your own tool: https://clig.dev/
I always appreciate tools with examples and a good help text. Also the ability to pipe with stdin/stdout if possible.
- Ask HN: Where to read about terminal UIs?
-
Ask HN: Do you read Secrets from Environment Variables
The Command Line Interface Guidelines [1] says:
> Do not read secrets from environment variables
> Secrets should only be accepted via credential files, pipes, `AF_UNIX` sockets, secret management services, or another IPC mechanism
Which one of these do you use? On github it seems common for projects to use environment variables for secrets.
[1] https://clig.dev/#environment-variables
-
Command Line Interface Guidelines
Seems they took a small step back from their previous "don't bother with man pages" stance. Now it's "Consider providing man pages."
I still find it a rather shocking order of priority, honestly.
https://clig.dev/#documentation
-
Ask HN: Best way to do scoped commands in a CLI app
- E. `blah project foo --edit`
Wondering if there was any guidance on this from the UNIX people. Perhaps scoping should be done using the file system. `cd path/to/project && blah edit`. Like git does with `git --cwd=path/to/project`. Maybe a virtual FS could even be used. Then you wouldn't have to continuously type in the scope with each command. Interesting thinking about how to maintain state in the terminal...thinking about how Python's virtual env bin/activate modifies the shell.
Found an interesting guide here: https://clig.dev/
-
A note from our sponsor - SaaSHub
www.saashub.com | 25 Apr 2025
Stats
Basic cli-guidelines repo stats
56
3,168
5.8
4 months ago
cli-guidelines/cli-guidelines is an open source project licensed under Creative Commons Attribution Share Alike 4.0 which is not an OSI approved license.
The primary programming language of cli-guidelines is CSS.
Popular Comparisons
Sponsored
InfluxDB high-performance time series database
Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
influxdata.com