@@ -1,23 +1,17 @@
-## Description
-
 <!--
-- Reference relevant issues or related pull requests with their URL / #<number>.
-- Use `pre-commit` to check and format code.
--->
+Please see the Contribution Guide:
+https://scikit-image.org/docs/dev/development/contribute.html
+For newcomers: this document has a checklist of what we expect in a PR.
 
-## Checklist
-
-<!-- Before pull requests can be merged, they should provide: -->
+Also please note our AI policy:
+https://scikit-image.org/docs/dev/development/contribute.html#ai-policy
+-->
 
-- A descriptive but concise pull request title
-- [Docstrings for all functions](https://github.com/numpy/numpydoc/blob/main/doc/example.py)
-- [Unit tests](https://scikit-image.org/docs/dev/development/contribute.html#testing)
-- A gallery example in `./doc/examples` for new features
-- [Contribution guide](https://scikit-image.org/docs/dev/development/contribute.html) is followed
+<!-- ... PR description goes here ... -->
 
-## Release note
+### Release note (optional)
 
-For maintainers and optionally contributors, please refer to the [instructions](https://scikit-image.org/docs/stable/development/contribute.html#documenting-changes) on how to document this PR for the release notes.
+<!-- See https://scikit-image.org/docs/stable/development/contribute.html#documenting-changes -->
 
 ```release-note
 ...
 
@@ -85,21 +85,28 @@ can be contributed to scikit-image.
      Please write `good commit messages
      <https://vxlabs.com/software-development-handbook/#good-commit-messages>`_.
 
-3. To submit your contribution:
+   * It is a good idea to read our :ref:`guidelines` at this point.
+     While we don't require a contribution to meet every guideline from the
+     start, they will come up during review.
 
-   * Push your changes back to your fork on GitHub:
+3. To submit your contribution:
 
-     ::
+   * Push your changes back to your fork on GitHub::
 
        git push codemonkey transform-speedups
 
      A message will be displayed with a URL to open in your browser to create a
-     pull request (PR). Open it and click the green button.
+     pull request (PR).
 
-.. tip::
+   * Before submitting the pull request:
 
-   If you get stuck, reach out to us on
-   `our Zulip chat <https://skimage.zulipchat.com/>`__.
+     - Use a concise, descriptive title
+     - Describe and link relevant context in the description
+     - Disclose all *generative* tools (AI, LLMs, agents) that you used, see our
+       :ref:`ai-policy` for details.
+
+   .. tip:: If you get stuck, reach out to us on
+      `our Zulip chat <https://skimage.zulipchat.com/>`__.
 
 4. Review process:
 
@@ -181,6 +188,30 @@ to make conflict markers easier to read.
 An alternative to merging is to rebase your branch—but we squash and merge all
 PRs anyway, so we don't mind merge commits.
 
+.. _ai-policy:
+
+AI Policy
+---------
+Regardless of how a PR was produced, scikit-image requires that
+authors illustrate a thorough understanding of any proposed changes.
+You **must review such code line-by-line**—it is **your
+responsibility** to ensure that it is correct, and that it does not
+breach copyright. You should expect the team to ask questions about
+your work.
+
+scikit-image is technically complex, key infrastructure; therefore, we
+place a high premium on correctness, and on avoiding technical
+complexity that may affect maintainability. If you want to make use of
+LLMs in a significant way, it is a good idea to **check in with us
+first**. Regardless, **always declare tool usage**.
+
+AI agents that have followed all guidelines in this document (outside
+of this section) may add 🤖 to their PR title. This signals to
+maintainers that the agent has self-verified compliance, enabling
+expedited review and acceptance.
+
+.. _guidelines:
+
 Guidelines
 ----------