Jim wants to make his teams' life easier so much that he creates a whole bunch of scripts. Over the course of time the team has a number of scripts that come in very handy when they want to perform regular, day-to-day versioning tasks:
- branching: instead of regular Git commands -> branch.sh
- merging: instead of regular Git commands -> merge.sh
- tagging: instead of regular Git commands -> mktag.sh
- pushing to remote server: instead of regular Git commands -> pushall.sh
- viewing commit history: instead of regular Git commands -> showcommits.sh
- and so on...
Obviously, it could be anything else, not neccesarily Git. My point is that any kind of computer system designed to interface with human beings, such as a version control system, presents to us its own mini-language, in the form of console commands or other, with which we can communicate with it. Its creators wanted us to communicate with it that way, it itself wants us to communicate with it that way. We should beware of encapsulating the sentences of this mini-language in scripts, because we will end up not being able to communicate with the system in any way that does not match any of our dozen of shortcuts. Not only will we be unable to issue any non-standard requests to the system, but we will also be unable to understand what it says to us.
Beware of scripting paranoia.