self-review

# Self-review Runs the same rubric as the `@claude` CI reviewer, so you catch issues before a maintainer does — but over your **whole** PR diff. (The CI scopes itself to `src/diffusers/`, `tests/`, and `.ai/`; for your own PR, also review your docs and scripts.) You're already on the branch with the conventions loaded, so: get the diff → review it against the rubric → report → iterate with the contributor until it's ready, then remind them to share the final notes on the PR. ## 1. Get the diff ```bash git diff main...HEAD # use your target branch if not main ``` If the branch trails `main` and the diff looks polluted with unrelated merged files, scope to your own commits: `git log main..HEAD --oneline`, then `git show <commit>`. ## 2. Read the rubric `references/review-rules.md` is the canonical rubric (the CI pins it from `main`) — read it and review against it; don't rely on a remembered copy. For the areas you touched, also read `references/code_style.md`, `references/models.md`, `references/pipelines.md`, `references/modular.md`, `references/testing.md`, or `references/pitfalls.md`. ## 3. Report - **Blocking issues** — numbered. Each: title → explanation → `file.py:line` → impact. Cite the rule, e.g. *Per `references/models.md`: "…only keep the inference path."* - **Non-blocking issues** — same format, lower severity. - **Dead code (advisory)** — a table: `path:line` · Likely-dead / Used · reason. - **Summary** — short synthesis and a verdict (**READY**...