I'm not totally sure what the point of this is. This is advertised as exit codes "for humans and machines", however<p>* humans will always get way more information from a readable error message printed to stderr before exiting<p>* machines do not care about error details from third-party tools, apart from whether they are an input error (which can be blamed on the user, if they provided said input) or an internal error (including usage error) which is a bug and should be fixed by the calling program's developer<p>Indeed, the README has a lot of examples of using it in your child program, to report error, but no example of a parent program dealing with the reported error.
It seems to be a Ruby equivalent to sysexits.h.[1] I don't know how widely used the codes are, but the idea is neat.<p>[1] <a href="https://manpage.me/index.cgi?apropos=0&q=sysexits&sektion=0&manpath=FreeBSD+12-RELEASE&arch=default&format=html" rel="nofollow">https://manpage.me/index.cgi?apropos=0&q=sysexits&sektion=0&...</a>