like oclif has

heya,

this looks fab! One thing I've been wondering about is some sort of self-documenting/completing mechanism - e.g. some way for bins/scripts to act as their own completer.

having a way to get a usage spec out of a script/bin (e.g. your double-shebang mechanism) is one half, but the other is for the command itself to be recursively involved in completions. Think e.g. a field that wants an s3:// url, or an scp remotehost:/remotepath field. Not fleshed out sorry, I'll come back to this :)

Apologies if this isn't the right spot. This issue is shared a bit between mise and usage.

I've recently started getting the Error: usage not found. message when attempting tab completions when using mise. I can go ahead and install mise, but it would certainly be handy if there was a usage and usage-bin package available in the AUR. I'd be happy to create such a thing but I'm aware you've already got release scripts set up for mise, so I thought it'd be worth asking in case you'd like to set up a similar thing for usage.

The other thing I'd wonder is whether mise and mise-bin should get updated so that they list usage as a dependency in the AUR. Happy to raise a separate issue in the mise repo for that though.

The dokku project uses some faux reflection and fancy footwork to generate cli help output as well as markdown docs from files. One thing that is nice is that we can show examples to users for usage.

I'm wondering if that would be possible to somehow spec out. Examples have a cli command as well as a description of the command, and are shown in the section for that particular subcommand.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

usage should complete things like the mise env --shell value