1
0
mirror of https://github.com/huggingface/diffusers.git synced 2026-10-24 20:59:27 +03:00
Files
diffusers/.github/PULL_REQUEST_TEMPLATE.md
YiYi Xu 662a6a354f ask to share self-review notes (#14185)
* Require sharing self-review notes on PRs

The PR template's self-review checkbox is unverifiable on its own — make the
notes a required, shareable artifact:

- self-review skill: new step to save each round's report and post all rounds
  on the PR (description or comment)
- contribution guide: sharing the notes is part of the AI-assisted
  contribution workflow; a checked box without notes counts as not done
- PR template: checkbox for having shared the notes
- .ai/AGENTS.md: mention the notes-sharing step in the self-review section

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Share only the final self-review round, not all rounds

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Mention self-review notes in the PR template intro comment

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Soften notes-sharing ask; skill iterates until ready then reminds to share

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Apply suggestion from @yiyixuxu

* Point checkbox and guide at the self-review skill directly

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Note human review comments as a source for agent doc gaps

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-14 18:10:30 -10:00

3.6 KiB

What does this PR do?

Fixes # (issue)

Before submitting

  • Did you use an AI agent (Claude Code, Codex, Cursor, etc.) to help with this PR? If so:
    • Did you read the Coding with AI agents guide?
    • Did you run the self-review skill on the diff?
    • Did you share the final self-review notes in the PR description or a comment?
  • Did you read the contributor guideline?
  • Did you read our philosophy doc? (important for complex PRs)
  • Was this discussed/approved via a GitHub issue or the forum? Please add a link to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the documentation guidelines, and here are tips on formatting docstrings.
  • Did you write any new necessary tests?
  • Are you the author (or part of the team) of the model/pipeline (only applicable for model/pipeline related PRs)?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR.