Turn a prompt you keep retyping into a Copilot prompt file instead of pasting it again

Write a reusable Copilot Chat prompt file, ready to save at .github/prompts/changelog-entry.prompt.md. The filename
becomes the slash command you type in the Chat input box to invoke it, so name the file for
exactly the command you want to type.

TASK THIS PROMPT FILE SHOULD DO EVERY TIME IT IS INVOKED
Read the staged diff and the most recent five entries in CHANGELOG.md, then draft one new entry in the same format and tone as the existing ones.

INPUTS IT SHOULD ACCEPT WHEN INVOKED
An optional short label for the type of change — feature, fix, or chore — defaulting to inferring it from the diff if omitted.

STRUCTURE THE FILE AS
1. YAML frontmatter: mode (ask — this only reads and drafts text, it never edits CHANGELOG.md directly. — pick the narrowest mode that can actually do the
   job; do not default to an editing-capable mode for a task that only needs to read and answer),
   tools (only if the mode is edit- or agent-capable and the task genuinely needs specific tool
   access, listed explicitly rather than inherited broadly), and description (one sentence
   describing the command, since this is what shows in the slash-command list when a user types
   the trigger character and starts scrolling).
2. The body, written as a direct instruction to Copilot, with the accepted inputs from
   An optional short label for the type of change — feature, fix, or chore — defaulting to inferring it from the diff if omitted. referenced using the prompt-files feature's own input-placeholder
   syntax rather than typed out as a literal string the user is expected to manually substitute
   themselves — the whole benefit of a prompt file over a saved snippet is that the input gets
   filled in at invocation time, not read and re-typed by a human first.
3. An explicit output contract at the end of the body: the exact section headers or shape this
   prompt file must produce every time, so invoking it on Monday and again on Friday, on different
   input, produces comparably structured output rather than two differently organized answers
   that happen to share a slash command.

HOW THIS DIFFERS FROM A CUSTOM CHAT MODE
A prompt file is one task invoked with one command and closed; a custom chat mode is a whole
conversational stance you switch into and stay in across many turns. If what you actually want is
a standing way of talking to Copilot for an entire session rather than a single repeatable task
with inputs, a chat mode is the better fit — do not force a multi-turn workflow into a single
prompt-file invocation just because a prompt file was the first mechanism that came to mind.

CONSTRAINTS
- If Read the staged diff and the most recent five entries in CHANGELOG.md, then draft one new entry in the same format and tone as the existing ones. genuinely needs file or workspace context beyond the invocation-time
  input, say explicitly what that context is rather than assuming Copilot will infer it from the
  current tab, since a prompt file is often invoked from a different file than the one its author
  had open while writing it.
- Do not have this prompt file perform a mutating action unless ask — this only reads and drafts text, it never edits CHANGELOG.md directly. explicitly calls
  for an editing-capable mode and the task genuinely requires it — a prompt file meant to be run
  repeatedly and quickly should not surprise its user with an unexpected file change.
- If .github/prompts/ currently has commit-message.prompt.md and pr-description.prompt.md. already has a prompt file doing something similar, name the overlap
  rather than adding a near-duplicate command that a future user will not know which one to reach
  for.

OUTPUT
The complete file content, frontmatter and body, ready to paste as-is. After it, one sentence
stating what this prompt file explicitly does not do that a user might otherwise assume from its
name.