google · kavinkumar807 · May 3, 2025 · May 3, 2025 · May 3, 2025 · May 3, 2025
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -112,7 +112,10 @@ For any changes that impact user-facing documentation (guides, API reference, tu
 
     ```shell
     python -m venv .venv
+
     source .venv/bin/activate
+    source .\.venv\Scripts\activate [windows]
+
     pip install uv
     ```
 
@@ -131,8 +134,36 @@ For any changes that impact user-facing documentation (guides, API reference, tu
     ```shell
     uv run pyink  --config pyproject.toml ./src
     ```
-
-## Code reviews
+
+6. **Build the package**
+    ```shell
+    uv build
+    ```
+
+7. **Local Testing**
+    Have a simple testing folder setup as mentioned in the [quickstart](https://google.github.io/adk-docs/get-started/quickstart/)
+        then install the local package with changes after building it using the below command to test the changes.
+
+    ```shell
+    uv pip install <YOUR_WHL_FILE_PATH>
+
+    [eg]: uv pip install <ADK_PROJECT_PATH>/dist/google_adk-0.4.0-py3-none-any.whl
+    ```
+
+### Requirement for PRs
+
+- All PRs, other than small documentation or typo fixes, should have a Issue assoicated. If not, please create one. 
+- Small, focused PRs. Keep changes minimal—one concern per PR.
+- For bug fixes or features, please provide logs or screenshot after the fix is applied to help reviewers better understand the fix.
+- Please add corresponding testing for your code change if it's not covered by existing tests.
+
+### Large or Complex Changes
+For substantial features or architectural revisions:
+
+- Open an Issue First: Outline your proposal, including design considerations and impact.
+- Gather Feedback: Discuss with maintainers and the community to ensure alignment and avoid duplicate work
+
+### Code reviews
 
 All submissions, including submissions by project members, require review. We
 use GitHub pull requests for this purpose. Consult