fix(docs): update contributing guide

Author: dineshpinto

CONTRIBUTING.md

@@ -6,8 +6,13 @@ We welcome contributions from the community to help make this SDK robust, featur
 
 ## How to Contribute
 
-- **Pull Requests (PRs)** for bug fixes, features, and documentation updates.
-- **Bug Reports** for issues you encounter.
+1. Search existing issues/PRs to avoid duplicates.
+2. For opening an issue, use labels `bug`, `feature`, `docs`, or `question`.
+3. Fork the repo and create a feature branch:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+4. Implement, test, then submit a PR referencing the issue.
 
 ## ✨ Write High-Quality Code
 
@@ -19,12 +24,17 @@ We strive for high-quality, maintainable code. Please adhere to the following pr
     - Design clear, minimal, and predictable interfaces for functions and classes.
     - Use descriptive names for variables, functions, and classes.
     - Keep code focused and avoid unnecessary complexity.
+    - Use [Google-style](https://google.github.io/styleguide/pyguide.html#38-comments-and-docstrings) docstrings.
 
-2.  **Formatting, Linting & Type-Checking:**
+2.  **Use dependencies sparingly:**
+
+    - Every dependency added is a potential security risk.
+    - If the dependency is required, it should live in under `[project.optional-dependencies]` with a key marking the high level function, e.g. `rag`, `consensus`.
+
+3.  **Formatting, Linting & Type-Checking:**
 
     - Use [ruff](https://docs.astral.sh/ruff/) for formatting and linting, both settings are defined in `pyproject.toml`.
-    - Use [pyright](https://github.com/microsoft/pyright) for type checking, all new code MUST include accurate type hints.
-    - Avoid using `typing.Any` unless absolutely necessary and clearly justified in comments.
+    - Use [pyright](https://github.com/microsoft/pyright) for type checking, all new code MUST include accurate type hints. Avoid using `typing.Any` unless absolutely necessary and clearly justified in comments.
     - You can also install [Pylance](https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance) into VSCode for an easier experience.
     - Ensure your code passes all checks locally without errors:
       ```bash
@@ -33,37 +43,37 @@ We strive for high-quality, maintainable code. Please adhere to the following pr
       uv run pyright
       ```
 
-3.  **Use dependencies sparingly:**
-    - Every dependency added is a potential security risk.
-    - If the dependency is required, it should live in under `[project.optional-dependencies]` with a key marking the high level function, e.g. `rag`, `consensus`.
-
-## 🧪 Test Extensively
+4.  **Test Extensively:**
 
-- New features **must** include appropriate unit and/or integration tests using `pytest`.
-- Bug fixes **should** include tests demonstrating the fix.
-- **All tests must pass** locally before submitting a pull request. Run tests via:
+    - New features **must** include appropriate unit and/or integration tests using `pytest`.
+    - Bug fixes **should** include tests demonstrating the fix.
+    - **All tests must pass** locally before submitting a pull request. Run tests via:
+      ```bash
+      uv run pytest tests/unit/your-test.py -v
+      uv run pytest tests/integration/your-test.py -v
+      ```
 
-  ```bash
-  # Run all tests (unit + integration, requires env vars for integration)
-  uv run pytest
-  ```
+5.  **Use Conventional Commits:**
 
-## 🚨 CI Checks Must Pass
+    - All commit messages **must** adhere to the **Conventional Commits** specification. This helps automate changelog generation and provides a clear commit history.
+    - Read the spec: [https://www.conventionalcommits.org/](https://www.conventionalcommits.org/)
+    - **Format:** `<type>[optional scope]: <description>`
+    - **Examples:**
+      - `feat(rag): add support for Neo4j AuraDB connection`
+      - `fix(ecosystem): correct decimal calculation in FTSO price feed`
+      - `docs(readme): update README with installation instructions`
+      - `test(rag): add unit tests for GraphDbSettingsModel`
+      - `chore(deps): update ruff version in pyproject.toml`
 
-- We use Continuous Integration (CI) pipelines (e.g., GitHub Actions) to automatically run linters, type checkers, and tests.
-- **Pull requests will only be considered for merging if all CI checks pass.** Ensure your code meets all quality gates before submitting.
+## 🚨 PR Checklist
 
-## ✅ Use Conventional Commits
+Before you mark your PR as ready-to-review:
 
-- All commit messages **MUST** adhere to the **Conventional Commits** specification. This helps automate changelog generation and provides a clear commit history.
-- Please read the specification: [https://www.conventionalcommits.org/](https://www.conventionalcommits.org/)
-- **Format:** `<type>[optional scope]: <description>`
-- **Examples:**
-  - `feat(rag): add support for Neo4j AuraDB connection`
-  - `fix(ecosystem): correct decimal calculation in FTSO price feed`
-  - `docs(readme): update README with installation instructions`
-  - `test(rag): add unit tests for GraphDbSettingsModel`
-  - `chore(deps): update ruff version in pyproject.toml`
+- [ ] Branch is up-to-date with `main`.
+- [ ] All linting, formatting, and type checks pass.
+- [ ] Tests cover new code (unit + integration).
+- [ ] Commit messages follow Conventional Commits.
+- [ ] PR description includes purpose and implementation details.
 
 ## 📜 License