diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index d12cda804156..32fab6f55b39 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,23 +1,19 @@
 <!--
 Read the Contributing guidelines first: https://github.com/getsentry/sentry-javascript/blob/develop/CONTRIBUTING.md
-
-Before you request a review:
-
-- Add tests for new or changed behavior. `pnpm run lint` and `pnpm run test` pass.
-- Fix or dismiss AI review findings.
-- Read your own diff first, add inline comments with explanation or where to look closely.
-- Large PR? Split or stack it, or describe why you cannot.
-
-- Remove fields that do not apply (e.g. on small PRs).
-- External contributors: link an issue where you got a maintainer's go-ahead.
+Use simple, direct sentences. No "Summary" heading, no test-plan checklist.
+Remove "Closes" if there is no linked issue.
+External contributors: link an issue where you got a maintainer's go-ahead.
 -->
 
-**Why:** <!-- reason behind change, why this approach (no implementation walkthrough), non-obvious decisions/tradeoffs -->
+## What
 
-**How to review:** <!-- where to start, what to skim -->
+<!--
+One or two sentences on what changed for users. Add one-line bullets for the changes if needed.
+Describe behavior and intent, not implementation. Reviewers read the diff for the how.
+-->
 
-**Unsure about:** <!-- where you want a second opinion -->
+## Why
 
-Closes #
+<!-- One or two sentences: reason behind change, why this approach (no implementation walkthrough), non-obvious decisions/tradeoffs -->
 
-<!-- Long, AI-written descriptions at the end, inside `<details><summary>AI walkthrough</summary>...</details>` -->
+Closes: #