From 4c8471484f72a867f4094ae205f0e5d85a966c38 Mon Sep 17 00:00:00 2001
From: GaganSD <gagandevagiri@gmail.com>
Date: Mon, 26 Oct 2026 02:08:48 +0530
Subject: [PATCH 1/4] docs: add pull request description template

---
 .github/pull_request_template.md | 45 ++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..8b46d4a
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,45 @@
+<!-- Keep this concise and high-level. Remove optional sections that do not apply. -->
+
+## Summary
+
+<!-- What changed and why? Mention the affected package(s) or shared tooling at a high level. Prefer 200 words or fewer. -->
+-
+
+## Related issues
+
+<!-- Link relevant issues (e.g. "Closes #123"), or write "None". An issue is optional. -->
+-
+
+## Testing
+
+<!--
+- List commands run and their results, plus relevant manual checks.
+- For package changes, use npm run <script> --prefix <package>:
+  lint, typecheck, test, build
+
+- For shared tooling changes: npm run test:tooling
+- For Pi behavior/UI changes, describe how you verified the change in Pi.
+- If a check was not run, say why. Docs-only changes can say "Not run (docs only)".
+-->
+-
+
+## Compatibility
+
+<!-- Note breaking changes, new dependencies, configuration/permission changes,
+or migration steps. Write "None" if there are no compatibility concerns. -->
+-
+
+## Risk
+
+<!-- What could this change break? Be specific, or explain why the risk is low. -->
+-
+
+## Screenshots / recordings (optional)
+
+<!-- For visible UI changes, show before/after where useful. Redact secrets and personal data. -->
+
+## Checklist
+
+- [ ] The change is focused; unrelated changes are excluded.
+- [ ] Tests cover behavior changes, or the testing section explains why not.
+- [ ] Relevant documentation is updated, or no documentation changes are needed.

From 251892c73f96a7b0b7e47fc7aec7a46839c7ed1e Mon Sep 17 00:00:00 2001
From: GaganSD <gagandevagiri@gmail.com>
Date: Mon, 26 Oct 2026 02:10:53 +0530
Subject: [PATCH 2/4] docs: separate PR summary from what and why

---
 .github/pull_request_template.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 8b46d4a..621341b 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -2,7 +2,17 @@
 
 ## Summary
 
-<!-- What changed and why? Mention the affected package(s) or shared tooling at a high level. Prefer 200 words or fewer. -->
+<!-- Give a high-level overview in 200 words or fewer. Use bullet points. -->
+-
+
+## What
+
+<!-- What changed? Mention the affected package(s) or shared tooling. -->
+-
+
+## Why
+
+<!-- What problem does this solve, and why this approach? -->
 -
 
 ## Related issues

From dc16ce7f0597ae8096a494dc077add8ab5ec0824 Mon Sep 17 00:00:00 2001
From: GaganSD <gagandevagiri@gmail.com>
Date: Mon, 26 Oct 2026 02:17:17 +0530
Subject: [PATCH 3/4] docs: add minimal bug and feature issue forms

---
 .github/ISSUE_TEMPLATE/bug.yml     | 30 ++++++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/feature.yml | 22 ++++++++++++++++++++++
 2 files changed, 52 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/bug.yml
 create mode 100644 .github/ISSUE_TEMPLATE/feature.yml

diff --git a/.github/ISSUE_TEMPLATE/bug.yml b/.github/ISSUE_TEMPLATE/bug.yml
new file mode 100644
index 0000000..54370ba
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug.yml
@@ -0,0 +1,30 @@
+name: Bug report
+description: Report something that is not working.
+labels: ["Bug"]
+body:
+  - type: input
+    id: environment
+    attributes:
+      label: Extension and versions
+      description: Include the affected extension, Pi version, Node.js version, and OS.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Provide the smallest example or steps that reproduce the bug.
+    validations:
+      required: true
+  - type: textarea
+    id: behavior
+    attributes:
+      label: Expected and actual behavior
+      description: What did you expect, and what happened instead?
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Logs or screenshots (optional)
+      description: Redact secrets and personal information before posting.
diff --git a/.github/ISSUE_TEMPLATE/feature.yml b/.github/ISSUE_TEMPLATE/feature.yml
new file mode 100644
index 0000000..933cc07
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature.yml
@@ -0,0 +1,22 @@
+name: Feature request
+description: Suggest an improvement.
+labels: ["Feature Request"]
+body:
+  - type: input
+    id: scope
+    attributes:
+      label: Affected extension or area
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem or use case
+      description: What are you trying to do, and what is missing today?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Suggested solution or alternatives (optional)
+      description: How might this work? Other approaches are welcome.

From 1d3661d0e0e8ba488090c4198d91d922bcc5df77 Mon Sep 17 00:00:00 2001
From: Gagan <gagandevagiri@gmail.com>
Date: Mon, 26 Oct 2026 02:24:32 +0530
Subject: [PATCH 4/4] Update pull_request_template.md

---
 .github/pull_request_template.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 621341b..d20e821 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -2,16 +2,15 @@
 
 ## Summary
 
-<!-- Give a high-level overview in 200 words or fewer. Use bullet points. -->
+<!-- Give a high-level overview in 150 words or fewer. -->
 -
 
 ## What
 
-<!-- What changed? Mention the affected package(s) or shared tooling. -->
+<!-- What changed? Mention the affected package(s), code, or shared tooling -->
 -
 
 ## Why
-
 <!-- What problem does this solve, and why this approach? -->
 -
 
@@ -23,10 +22,9 @@
 ## Testing
 
 <!--
-- List commands run and their results, plus relevant manual checks.
+- List pi version, commands run and their results, plus relevant manual checks.
 - For package changes, use npm run <script> --prefix <package>:
   lint, typecheck, test, build
-
 - For shared tooling changes: npm run test:tooling
 - For Pi behavior/UI changes, describe how you verified the change in Pi.
 - If a check was not run, say why. Docs-only changes can say "Not run (docs only)".