diff --git a/docs/pull_request_template.md b/docs/pull_request_template.md
new file mode 100644
index 0000000..dffa622
--- /dev/null
+++ b/docs/pull_request_template.md
@@ -0,0 +1,35 @@
+## 🌟 Purpose
+
+<!--
+Required. Must be written by a human, as short sentences or bullets.
+-> Why are you making this change? Start with the problem or request, e.g. "The frontend fails on X because Y."
+-> Then say in a few sentences what the PR does.
+-> Link a doc or discussion the reader needs for context, don't include link to PRs which PR is stacked on, and don't add links to this linear issue (if multiple linear issues are done as part of this PR, include them all in a comma-separated list in the PR title).
+-> For a UI change, add a screenshot or recording here, and the steps to see it working.
+-> Do not reveal internal client or security-specific motivations in the description.
+-->
+
+## 🔍 Changes
+
+<!--
+Required unless the purpose already says everything that changed, delete this section otherwise.
+-> What should a reviewer know before opening the diff?
+-> Pick the most important changes that matter, say why anything surprising changed, and for a big PR, where to start.
+-> don't list every file or function you changed
+-> This section should help the reviewer to understand changes that won't be self-evident from reading down the diff, either because they span multiple files, are complex, or would seem unconnected to the primary goal.
+-> Do not reveal internal client or security-specific changes.
+-->
+
+## ⚠️ Known issues
+
+<!--
+Required if something is broken, unfinished or breaking, e.g. it's behind a feature flag or the fix comes next. Delete this section otherwise.
+-> Do not reveal internal client or security-specific issues.
+-->
+
+## 🚫 Blocked by
+
+<!--
+Describe anything that must be done before the PR is merged, for example further testing, deployment of something, etc. Delete this section otherwise.
+-> Never include dependencies that are already obvious in GitHub (stacked branches).
+-->