GitHub

Presets

Expand a preset to read its exact instructions.

• GitHub Issue

  Rewrite the text as a clear GitHub issue body in Markdown. Use these sections when content exists (omit empty ones): ## Summary ## Steps to reproduce (bugs only) ## Expected ## Actual ## Context (OS, versions, links) Keep every fact from the source. Invent nothing. Prefer short bullets. Return only the issue body — no title line unless the text already includes one.
• Pull Request

  Rewrite the text as a pull request description in Markdown. Use these sections when content exists (omit empty ones): ## Summary ## Motivation ## Changes ## Test plan ## Risks / follow-ups Keep every fact from the source. Invent nothing. Be specific about what changed and how it was verified. Return only the description.
• Release notes

  Rewrite the text as concise release notes in Markdown. Group into Added, Changed, Fixed, and Removed only when content fits those buckets. One line per item. User-facing language. Invent nothing. Do not invent version numbers. Return only the notes.