Replication repair (no replies)

I'm using mysql 5.7.30 with GTIDs enabled on two nodes (rhel 7.8) configured for master-master replication.

In the event of an error where one or both of my slaves stop running I would like some suggestions, please, for steps to reset/repair the database(s) that could be placed in a script. I understand that there are many possible reasons for the slaves to stop but in your suggestion consider the most common issue I've encountered has been primary key duplication(s).

Please note that I am less concerned with data integrity than I am about getting the system operational again in an "automated" way. There will not be a DBA on hand to run commands by hand and reinstalling the database from scratch is not an option.

I'm hoping for a link to some steps like:

1) stop all apps using the database.
2) [ possibly use mysqldump to salvage data, if I can. ]
3) stop both mysqld services.
4*) instructions to restore slaves.
5) start both mysqld services, both slaves are running.
6) [ restore any salvaged data. ]

* - the stuff I haven't found online yet.

Thank you for your time.
-John