`git revert` is easy; a *safe production rollback* is not. On a stateful platform the code is only half the deployment — databases have installed modules, applied migrations, created records, and users have learned URLs. A revert PR that is technically clean can still ship surprises. This skill is the checklist that turns "revert that commit" into a correct, honestly-described rollback.
