I'm thinking of a book like Working Effectively With Legacy Code but that deals more with things like documentation, specification, code review, etc. I'd like the book to help with the following scenario: given some completely "naked" codebase, what things (whether they're specs, docs, comments, whatever) need to be added to the codebase before you'd consider it "high-quality"?
I would add Clean Code. It's Java centric but a lot of the ideas can be used in any language, even though it can probably all be condensed to "everything should do a single thing and no more"
Yeah, single responsibility principle is the key takeaway from that book. Clean Code is a must for all programmers and I can recommend it as a prequel to CA. It's written by the same author after all.
I have a feeling the OP is looking for a book about software development in a broad sense.
Not the person that you replied to, but he probably means the book on the right. It's a good recommendation especially if you are trying to understand how and why DevOps / SRE works and why it's important.
