I'm not quite sure what to write here, any suggestions? @fanninpm @youknowone

You could start with these sections:

• What changed: Requesting a description of what the pull request changes in the human's own words. Here the contributor can disclose the use of AI assistance, if applicable. (Coderabbit will make its own summary)
• Motivation: Requesting an explanation of why the pull request was made in the human's own words. (Language such as Closes #WXYZ should suffice, given some criteria [TODO: should be defined] that the linked issue has to meet.)
• Verification: Requesting a summary of what steps were taken to verify the effectiveness of the PR's changes.
• Checklist: Something like (with language to be refined):
  • If I changed something that impacts Rust code, I can confirm that I ran cargo whatever with no errors. (If not, please explain why.)
  • I can confirm that I ran (whatever other tool or tools (for the next few bullet points)) (If not, please explain why.)
  • If I have used AI assistance, I have disclosed it as such.
  • I understand that others, including the RustPython maintainers, will ask me questions about this pull request
  • I will respond to these questions in my own words to the best of my ability.
  • I understand that the RustPython maintainers will close my pull request if I do not check any of these boxes.

If you have anything to add to the checklist, it is a good idea to use the active voice in a manner similar to how I wrote the previous bullet points.

Separately from this PR, I think it would be a good idea to convert our Issue templates from Markdown into YAML format.

I liked that idea a lot. I've looked around in couple of FOSS projects and took what I liked. If you have a checkbox you would like to add/remove, please feel free to say (or even push it straight to my branch)

Separately from this PR, I think it would be a good idea to convert our Issue templates from Markdown into YAML format

I'll look into that:)

⚠️ Potential issue | 🔴 Critical

#!/bin/bash
# Description: Verify the AI policy document exists and is accessible

# Check if the AI policy file exists in the .github repository
gh api repos/RustPython/.github/contents/AI_POLICY.md --jq '.name' 2>/dev/null || echo "AI_POLICY.md not found in RustPython/.github repository"

# Also check the raw content availability
curl -s -o /dev/null -w "%{http_code}" https://raw.githubusercontent.com/RustPython/.github/main/AI_POLICY.md

The referenced AI policy document does not exist and must be created before merging.

The contribution guidelines require contributors to follow an AI policy at https://github.com/RustPython/.github/blob/main/AI_POLICY.md, but this document is not currently available in the RustPython/.github repository. The policy cannot be enforced or followed by contributors without this document. Either create the AI_POLICY.md file in the RustPython/.github repository or update the reference to point to an existing document.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CONTRIBUTING.md` around lines 20 - 21, CONTRIBUTING.md references a
non-existent AI policy at
https://github.com/RustPython/.github/blob/main/AI_POLICY.md; add the missing
AI_POLICY.md to the RustPython/.github repository (or update the link in
CONTRIBUTING.md) so the referenced policy exists. Create a clear AI_POLICY.md
file containing the project's AI usage rules and place it in the .github
repository root, then verify CONTRIBUTING.md's link points to that new file (or
change the link to an existing policy file) to ensure the guideline resolves
correctly.