self-review Skill
Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the @claude CI (checks the diff against .ai/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what Published by huggingface in diffusers.
What is self-review Skill?
Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the @claude CI (checks the diff against .ai/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what Published by huggingface in diffusers. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use self-review Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: huggingface
- Repository: huggingface/diffusers
- Skill file: .ai/skills/self-review/SKILL.md
What it does
Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the @claude CI (checks the diff against .ai/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what
Skill instructions
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/ and .ai/; for your own PR, also review your tests, docs, and scripts.) You're already on the branch with the conventions loaded, so: get the diff → review it against the rubric → report. 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 .ai/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 .ai/models.md, .ai/pipelines.md, or .ai/modular.md. 3. Report - Blocking issues — numbered. Each: title → explanation → file.py:line → impact. Cite the rule, e.g. Per .ai/models.md: "…only keep the infer
Explore related resources
Frequently asked questions
What is self-review?
self-review is a open-source AI agent skill with Copy skill directory. Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the @claude CI (checks the diff against .ai/review-rules.md, traces call paths for dead code).
Who is self-review best for?
self-review is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install self-review?
Install or run self-review using Copy skill directory. Check self-review for the latest setup command.
Is self-review actively maintained?
self-review may need a closer maintenance check before production use.
Auto-fetched from GitHub.
