CONSOLE-5204: Merge PR templates

AGENTS.md

@@ -88,6 +88,14 @@ go mod vendor && go mod tidy # Update Go dependencies
 - Subject line answers "what changed"; body answers "why"
 - Frontend i18n updates: Run `yarn i18n` and commit updated keys alongside any code changes that affect i18n
 
+### Pull request strategy
+
+- When opening a PR, make sure to fill out the PR template located in `docs/pull_request_template.md` with all required sections. This helps the OpenShift Console team triage, review, and verify the changes effectively.
+- Always link to the relevant JIRA issue in the PR title and description. If not provided prompt the user for the JIRA.
+- You cannot produce screenshots or screen recordings but leave the field there so the user can fill it out afterwards.
+- You can use the `gh` CLI to open a PR but ALWAYS prompt the user before doing so to confirm the PR title, description, and linked JIRA issue are correct.
+- If the `jira` CLI or MCP is available, use it to fill out the PR description as well as assignee(s).
+
 ### Branch naming
 
 - Feature work: `CONSOLE-####` (Jira story number)

docs/pull_request_template.md

@@ -0,0 +1,51 @@
+<!--
+  Please fill in every section below before requesting review. Filled-in descriptions are
+  required for the OpenShift Console team to triage the pull request, review the code, and
+  verify the behavior end-to-end.
+
+  The pull request title must be prefixed with a Jira issue in order to be merged. For example:
+
+  For e.g Features: https://redhat.atlassian.net/browse/CONSOLE-XXXX
+  - CONSOLE-XXXX: <title>
+  For e.g Jira Bug Fixes: https://redhat.atlassian.net/browse/OCPBUGS-XXXX
+  - OCPBUGS-XXXX: <title>
+-->
+
+**Analysis / Root cause**:
+<!-- Briefly describe analysis of US/Task or root cause of Defect -->
+
+**Solution description**:
+<!-- Describe your code changes in detail and explain the solution or functionality -->
+
+**Screenshots / screen recording**:
+<!-- Add screenshots or screen recordings for visual changes. Be sure to include before and after videos where relevant -->
+
+**Test setup:**
+<!-- If any setup required to test this PR, mention the details -->
+
+**Test cases:**
+<!-- List possible test cases to validate the changes. -->
+
+**Browser conformance**:
+<!-- To mark tested browsers, use [x] -->
+- [ ] Chrome
+- [ ] Firefox
+- [ ] Safari (or Epiphany on Linux)
+
+**Additional info:**
+<!-- Add any additional info here -->
+
+**Reviewers and assignees:**
+<!--
+- Tag an OCP console engineer to review the changes and verify the functionality.
+- If there are visual, content, or interaction changes in the PR, tag "@openshift/team-ux-review"
+- If the PR is implementing a story, assign Docs, and PX approvers:
+  Console Approver:
+  /assign <gh-user>
+
+  Docs approver:
+  /assign <gh-user>
+
+  PX approver:
+  /assign <gh-user>
+-->