[jlg23]

Did this a few times, devs loved it: all in posix-shell, the main script was a rather ugly thing but devs would never touch it. You'd code your command as a simple shell script in cli-lib/$username/$command, it would be available to you as 'cli $command', to others as 'cli $username.$command'.

Useful commands would be copied over into the directory that contains the commands accessible to all. Usefulness was determined at the coffee machine, the smokers' room or in conversations after presentations on their work given by devs.

Also, interested interns would be tasked to spot "optimization potential" - so they read through these commands, learned to read and write shell scripts and they had to learn to efficiently address senior devs.

Everytime this was more a social thing than actual workflow optimization: Tooling became a permant side project, people could (and would) look their peers' scripts, one could take a short break from the main project by working on this. One observation I made: the more senior the devs, the less interested they were in this "playground" - after all good devs are always faster at hacking solutions to these simple problems than evaluating and adapting existing ones.