Update CONTRIBUTING.md for agentic PRs

Signed-off-by: Vignesh Venkatasubramanian Vaidyanathan <62492557+VigneshVSV@users.noreply.github.com>

Author: VigneshVSV

CONTRIBUTING.md

@@ -20,6 +20,8 @@ All types of contributions are encouraged and valued.
 
 If you want to tackle any issues, un-existing features, please do have a look at [good-first-issues](https://github.com/hololinked-dev/hololinked/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). Issues are separated by perceived level of difficulty (`beginner`, `intermediate`) and type of contribution (`bug`, `feature`, `documentation` etc.). If you wish to propose a feature or bugfix, they are totally welcome and we could discuss it on discord/email (links in README) before you start working on it.
 
+Good first issues are meant for humans to practice coding, trying to understand the codebase, propose improvements or flaws while reviewing the codebase etc. Please refrain from automating PRs with low quality fixes. I can do most good first issues on my own without anybody's help, so introduce more machines here is not the point.  
+
 Partial contributions are also taken if its easier to continue working on it. In this case, you can submit your fork to merge into a separate branch, where someone else can develop it until it meets the required standards for release.
 
 To start developing and complete the contribution, following steps may be followed:
@@ -31,7 +33,7 @@ To start developing and complete the contribution, following steps may be follow
 5. Unit/Integration tests are recommended to be added for any new feature or bug fix. These tests can be run with `python -m unittest` under the `tests` directory.
 6. The CI pipeline currently enforces codestyle checks and tests, therefore steps 4 & 5 must be completed before making a pull request.
 7. Once you are done with your changes, make a pull request to the main repository. Your changes will be reviewed in detail and any review comments that may be added need to be resolved as well. When requirements are met and the pipeline passes, commits will be squashed and merged to the main branch.
-8. For AI generated code, please make sure to review it properly. You need to understand the code that you write or submit. Same applies to documentation, comments etc., please write them only to the extent you would be willing to read them later, not to bloat them with autogenerated text. A thumb rule is, if you cannot review your own generated code, I am not going to do it either. Submit only what you will review.
+8. For AI generated code, please make sure to review it properly. You need to understand the code that you write or submit. Same applies to documentation, comments etc., please write them only to the extent you would be willing to read them later, not to bloat them with autogenerated text. A thumb rule is, if you cannot review your own generated code, I am not going to do it either. Submit only what you will review. 
 
 There are also other repositories which can use your skills: