Suggestions for CLI applications wanted #42

Is it able to provide example of full dotnet CLI command?

.NET 10 SDK preview.6 support --cli-schema options.
So almost of parts can be mapped by --cli-schema output.

Azure CLI, especially for testing the size of the CLI and amount of commands

CLI for Microsoft 365, contains 800+ commands.

Aspire CLI - microsoft/aspire#12824

The Amper build tool (CLI page here) would also be a good example, as we make use of many features of the https://ajalt.github.io/clikt/ framework. Currently most things are impossible to express in the spec though, especially all the path type subtleties and the interaction between options (see #65).

If I can suggest an oddball CLI app, I think the Chess UCI protocol (standardized protocol chess engines must speak to be able to play against a human or other chess engines) would be interesting. It has more 'state', meaning a session would look like:

% stockfish
Stockfish 17 by the Stockfish developers (see AUTHORS file)
> uci
id name Stockfish 17
id author the Stockfish developers (see AUTHORS file)
option name Debug Log File type string default <empty>
option name NumaPolicy type string default auto
option name Threads type spin default 1 min 1 max 1024
option name Hash type spin default 16 min 1 max 33554432
....more options
uciok
> position fen rnb2bnr/pppp1k1p/5q2/8/5p2/4BQ2/PPP3PP/RN3RK1 w - - 2 11
> go
info string Available processors: 0-11
info string Using 1 thread
info string NNUE evaluation using nn-1111cefa1111.nnue (133MiB, (22528, 3072, 15, 32, 1))
info string NNUE evaluation using nn-37f18f62d772.nnue (6MiB, (22528, 128, 15, 32, 1))
info depth 1 seldepth 3 multipv 1 score cp -241 nodes 67 nps 22333 hashfull 0 tbhits 0 time 3 pv e3f4

The specification is
engine-interface.txt (source)

I think FFMpeg would be great to stress spec. Same for Unix tools. AWK?

Docker, kubectl, popular unix tools would be great addition.