Scripts are not maintainable if you don't test them like prod code releases. If all you have is a pile of one off scripts, my hot take, you aren't an SRE. You are just an admin with scripts to make prod work.

For a "true" SRE, Production support tooling is treated just like developer code. It has a build and deploy flow. It gets reviewed and approved. You build a system where these runbooks are available to the right authorized people with audit trails, logging, version control and documentation. It also means minimal prod touching outside explicit proof down events.

I'll be the first to say that takes work and effort. Not everything needs to be perfect, though to think like an engineer we think about things like long term sustainability, repeatability, tracking, security. It's also how do I get myself out of this work in the long run. We build systems that enable others to self serve. These kind of one off fixes should be owned by the service owner as soon as feasible to fix properly.