Quick way (Editor script?) to track conflicting actions and snuff 'em?

[Broken Stylus]

I've got a bunch of old custom actions that are now conflicting with their now "official" version that's part of the PM package.
Is there a quick way to target and delete the old custom actions, and even with a bit of log to provide information like, for example, if there also were fundamental differences inside their respective scripts, different code blocks, etc.?

[djaydino]

if you have duplicate errors, search the .cs file check the folder their in and remove the custom version.

you can open both files (best with visual studio) and you can look side to side for differences.

I don't think there is a better or quicker way

[Broken Stylus]

Yes, the manual sluggish way. Ah never mind.

[Christoph]

Could use something like this: https://www.diffchecker.com/ there are many others. Editor script for sure would be great.

[Broken Stylus]

I will likely have to look into an asset that can compare changes. From memory I think there exists a few. But it would not understand the actions like a Playmaker-made tool might.