@twowheels,
Just to expand a bit on what @geek1011 said ...
Every patch is contained in one of four .yaml files. A .yaml file can be opened (and edited) with any decent text editor. If you're a Windows user I'd recommend Notepad++.
Every patch has a name (the first line) and a description, which is as detailed as the patch creator decided to make it. Inside the description some patches contain an url link to a Mobileread or a GitHub post which contains more detail and (sometimes) screenshots to help illustrate what the patch does.
Some patches are simple enough that all you need to decide is
"do I want to enable this patch?", yes or no.
Other patches are more complex and have several options which allow you to customise some/all of the patch values to help meet your exact requirements. For these patches each option usually has some help notes written as comments
(line starts with a hash # character) to give you hints about how to make your personal customisations.
Once you've read a patch's description and help notes, if it's still not clear, then you can always ask for clarification. I'm sure both @geek1011 and myself will consider improving the detail inside the patch if it's not adequate.
At the end of the day, though, kobopatching is hacking, so it's definitely an "engage brain" activity.
Advanced technical skills are not necessary, but read-the-instructions skills are.
If you want to look at the kobopatch .yaml files you need to download the kobopatch zip file which corresponds to your current firmware, e.g. post #1, item 2 of
this thread for fw 4.23.15505.