Model PR Diff Dossier

Use this skill before publishing any model PR optimization history document that cites framework PRs.

Non-Negotiable Standard

Do not summarize a PR with only a title-level sentence. Do not use a script or bulk generator to fill motivation, implementation notes, or code excerpts.

For every PR cited as model optimization evidence, the document must include or link to a diff-reviewed PR card with:

• PR link, title, state, merge time when available, additions/deletions, and changed-file count.
• Motivation: why the PR existed, inferred from PR body, title, issue context, docs changes, tests, and code diff.
• Key implementation idea: what runtime path changed and how the patch implements the change.
• Key code excerpts: short, relevant snippets from the actual diff, not invented pseudocode.
• Reviewed files: important files from the full diff, grouped by runtime/docs/tests where possible.
• Validation implications: tests, benchmark paths, launch flags, or regression lanes implied by the diff.
• Diff coverage note: state that the full diff was fetched/read and include diff line count.