[aisk]

This adds a button that generates a prompt for users to copy into a web AI chat assistant, such as ChatGPT, Claude, Gemini or DeepSeek, to help write a NEWS entry.

When doing triage, I noticed that many new contributors have trouble writing a proper NEWS entry. This can be especially hard for people who are not native English speakers, or who are not familiar with RST and Sphinx markup. Reviewers often need to help fix the wording, the RST syntax, or the inline markup.

LLM (or AI) are good at this kind of writing task. But a direct LLM integration would be more complicated. We don't have free tokens for users, server-side AI calls could be abused and may introduce security issues. Let contributors to provide their own API keys are also not suitable, many contributor also may not have an API key.

Then I came up with an idea, it's a simpler approach that only generates a prompt. The prompt includes links to the issue, pull request, diff, changed files API, and guidance on how to write a NEWS entry. Users can paste it into a web AI chat assistant and use the result as a reference, which has a free usage quota.

I tested this with ChatGPT, Claude, Gemini and DeepSeek. For changes without very huge diffs, they can produce useful NEWS entry drafts as a reference.

The screen shot:

An generated prompt example for python/cpython#2210:

Please draft exactly one CPython Misc/NEWS entry for the following change.

## Context links 
- GitHub issue: https://github.com/python/cpython/issues/38066
- GitHub pull request: https://github.com/python/cpython/pull/2210
- Pull request diff: https://github.com/python/cpython/pull/2210.diff
- Changed files API: https://api.github.com/repos/python/cpython/pulls/2210/files

## Target NEWS section: IDLE

##Instructions

- Read the issue, pull request, diff, and changed files before drafting.
- First decide whether this change needs a NEWS entry.
- A NEWS entry is usually not needed for documentation changes, test changes, strictly internal changes with no user-visible effects, or changes that already have a NEWS entry.
- If a NEWS entry is probably not needed, say that the user may consider not writing one and wait for a core developer or triager to add the skip news label.
- Output only the NEWS entry text.

## How to write a NEWS entry

All `NEWS` entries end up being part of the changelog. The changelog contains a lot of entries, and its intended audience is mainly users, not core devs and contributors. Take this into consideration when wording your `NEWS` entry. Describe the user-visible effects of your change succinctly and accurately; avoid long technical elaborations, digressions, and do not expect or require the reader to have read the actual diff for the change.

The contents of a `NEWS` file should be valid reStructuredText. An 80 character column width should be used. There is no indentation or leading marker in the file, for example `-`. There is also no need to start the entry with the issue number since it is part of the file name. You can use inline markups too. Here is an example of a `NEWS` entry:

```rst
Fix warning message when :func:`os.chdir` fails inside
:func:`test.support.temp_cwd`.
```

The inline Sphinx roles like `:func:` can be used to help readers find more information. The user can build HTML and verify that the link target is appropriate by using `make html`.

Generate result by Claude:

[aisk]

I noticed that Claude generated the NEWS entry with “Contributed by Stan,” but Stan is only a co-author in this PR, not the original author.

I found that this is caused by the example NEWS entry including the "Contributed by ..." parts, so Claude want to use one, but It does not know the real name that the contributor wants to use here and may hallucinate one from history commits or it's training data.

I updated the generated prompt to remove this part in the NEWS entry, now it works well on Claude.

[hugovk]

I'm not keen on this. I expect it will result in NEWS files that are far too verbose.

[Mariatta]

This was discussed among core devs and the consesus is we'd much prefer writing a better instructions for contributors to understand and learn on how to write an effective and meaningful news entry, than to write how to prompt the LLM on how to do it.

So instead of adding how to prompt your LLM to write the entry, I opened https://github.com/python/devguide/pull/1928/changes for the contributors, and I will link to this from blurb-it and add a tip box so it will be helpful.