Added checklist to PR template to enforce standards

.github/pull_request_template.md

@@ -4,7 +4,7 @@ This section can be deleted after reading.
 We employ the following branching strategy to simplify the development process and to ensure that only stable code is pushed to the `master` branch:
 
 - `develop`: For unstable code: New features and bug fixes.
-- `master`: Where the stable production ready code lies. Only security related bugs.
+- `master`: Where the stable production-ready code lies. Only security-related bugs.
 
 NOTE!!!
 
@@ -27,6 +27,9 @@ Fixes #<!--Add related issue number here and delete this comment text block.-->
 
 <!--Yes or No. Note: Add unit tests or automation tests for your code.-->
 
+- [ ] Tests are written for all changes made in this PR.
+- [ ] Test coverage meets or exceeds the current coverage (~90/95%).
+
 **Snapshots/Videos:**
 
 <!--Add snapshots or videos wherever possible.-->
@@ -44,6 +47,10 @@ Fixes #<!--Add related issue number here and delete this comment text block.-->
 
 <!-- If this PR introduces a breaking change, please describe the impact and a migration path for existing applications. -->
 
+**Checklist for Repository Standards**
+- [ ] Have you implemented all relevant `coderaabbitai` suggestions?
+- [ ] Have you ensured that the PR aligns with the repository’s contribution guidelines?
+
 **Other information**
 
 <!--Add extra information about this PR here-->

CONTRIBUTING.md

@@ -250,6 +250,8 @@ The value of `safeBlockVertical` and `safeBlockHorizontal` will be displayed in
     - All your file should contain at max `300` lines of code.
     - Follow proper code formatting and run `flutter format .` before your PR.
     - Run `flutter analyze` before your PR and make sure to resolve all the found issues.
+    - Tests must be written for all code changes, ensuring they maintain or exceed the current code coverage threshold.
+    - Ensure your pull request is approved by Coderaabbitai by addressing and implementing all its suggestions.
 
 ### Project Structure