write-pr-description

A bug fix PR description should state what is broken, how to reproduce it, the root cause, what the fix changes, and how to verify it. This Skill routes bug PRs to a dedicated guide covering Summary, Purpose, Reproduction, Root cause, Fix, and How to verify sections.

An experiment PR description acts as a compact experiment record covering what was tested, why, the setup, a Mermaid flow diagram, the run command, and a results table. This Skill provides an experiment guide, template, and three worked examples including ablations and model comparisons.

A feature PR description should include a Summary, Purpose, Architecture with before/after Mermaid diagrams, Interfaces and contracts (endpoints, schemas, configuration), and How to run instructions. The Skill's feature guide and template define each section with examples.

Use the default type, a catch-all for refactors, chores, infra changes, docs, and dependency bumps. Its guide structures the description around Problem, Solution, Purpose, and How to run sections.

Yes, the guides call for Mermaid flowchart diagrams where they clarify the change. Feature PRs use before/after architecture diagrams, experiment PRs use pipeline flow diagrams, and bug fixes use before/after diagrams when control flow changes.