Please open an issue with a problem statement or feature request before submitting a pr. This allows for framing of a problem or a feature so that in the future a pr with irrelevant code is not included.
This should be written in a simple conscise manner.
Part of the contract of open source is that you must understand the code being submitted. If you don't understand it do not submit it.
Code review is meant to be a second set of eyes - it assumes that the submitter has already understood and vouches for the code they are submitting.
Overly verbose issues and pr descriptions should be avoided. You need to be able to clearly state what your change is doing and understand it so do not use AI for generating your commit message.
Large prs take a longer time to review so better to keep your prs smaller in scope.