From 08036b148d71a73544755eb30a19b500f55c37ad Mon Sep 17 00:00:00 2001
From: Samson Akol <akolson2010@gmail.com>
Date: Wed, 21 Oct 2026 16:05:54 +0300
Subject: [PATCH 1/2] Add the AI usage section and mark the required sections

This template predates the AI usage policy, so it never asked for the
disclosure that learningequality/.github's shared template asks for. The
wording of the section is copied from that template, so every repo asks the
same thing.

The REQUIRED markers tell the shared template check which sections a pull
request body must carry. A section without a marker stays optional, so the
sections this template invites a contributor to remove can still be removed.
---
 .github/PULL_REQUEST_TEMPLATE.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index df821875..788e9856 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,4 +1,5 @@
 ## Summary
+<!-- REQUIRED -->
 
 *Short description*
 
@@ -19,3 +20,31 @@ List the issues solved or partly solved by the PR
 ## Documentation
 
 If the PR has documentation, link the file here (either .rst in your repo or if built on Read The Docs)
+
+<!--
+AI USAGE - REQUIRED
+
+State explicitly whether you didn't use or used AI & how.
+
+If you used it, ensure that the PR is aligned with [Using AI](https://learningequality.org/contributing-to-our-open-code-base/#using-generative-ai as well) as well as our DEEP framework. DEEP asks you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Review code for correctness and unnecessary complexity.
+  Edit - Review and refine AI output. Remove unnecessary code and verify it still works after your edits.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Claude Code to implement the component, prompting it to follow
+  the pattern in ComponentX. I reviewed the generated code, removed
+  unnecessary error handling, and verified the tests pass."
+
+  "I brainstormed the approach with Gemini, then had it write failing
+  tests for the feature. After reviewing the tests, I used Claude Code
+  to generate the implementation. I refactored the output to reduce
+  verbosity and ran the full test suite."
+
+-->
+
+## AI usage
+<!-- REQUIRED -->

From ddcb0df7349fe1aa15986a3c53f0e871226796e9 Mon Sep 17 00:00:00 2001
From: Samson Akol <akolson2010@gmail.com>
Date: Wed, 21 Oct 2026 19:34:18 +0300
Subject: [PATCH 2/2] Put the AI usage comment under its heading

Every other section in this template carries its guidance comment after the
heading. The block added in the previous commit carried it before, so it read
as part of the section above it.

The comment also opened with "AI USAGE - REQUIRED", which the heading and the
REQUIRED marker now say.
---
 .github/PULL_REQUEST_TEMPLATE.md | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 788e9856..235ca2bb 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -21,9 +21,9 @@ List the issues solved or partly solved by the PR
 
 If the PR has documentation, link the file here (either .rst in your repo or if built on Read The Docs)
 
+## AI usage
+<!-- REQUIRED -->
 <!--
-AI USAGE - REQUIRED
-
 State explicitly whether you didn't use or used AI & how.
 
 If you used it, ensure that the PR is aligned with [Using AI](https://learningequality.org/contributing-to-our-open-code-base/#using-generative-ai as well) as well as our DEEP framework. DEEP asks you:
@@ -45,6 +45,3 @@ Examples of good disclosures:
   verbosity and ran the full test suite."
 
 -->
-
-## AI usage
-<!-- REQUIRED -->