You don't have to "learn every tool in depth." You do have to learn how to use the tools you depend on well enough to address your needs. I have used git/GitHu

You don't have to "learn every tool in depth." You do have to learn how to use the tools you depend on well enough to address your needs. I have used git/GitHub for years across multiple projects and have never needed to sort branches by status or recover a deleted branch. I try to close branches when done (after merging) and make sure they have descriptive names so I can search for them. You have different requirements, so either you learn to use the tools to meet those requirements or you change your workflow to fit what the tools can easily do. If you found bash scripts to do what you want then you didn't need to learn bash and sed and so on in depth, you only had to copy/paste the script and maybe change a couple of things. Learning the tools of the programming trade transfers across projects and jobs. Once you get comfortable with git, bash, sed, etc. you will have those skills for the rest of your career, and most likely those tools will live for a long time because they already have.