A ready-to-use system prompt for a changelog agent that explains what changed in a release and how it affects the user, drawn from your own release notes and cited — so "what's new" and "did this break my setup" get accurate answers. Copy it, fill the brackets, and paste it into your agent's instructions.
What this agent does
Users and developers track your releases to understand new features, breaking changes, and migration steps — but raw changelogs are terse. This prompt makes the agent explain a release in plain terms from your own notes, citing the entry, and connect it to what the user is asking ("is X still supported," "how do I migrate"). It stays grounded: when a release note doesn't cover an impact, it says so rather than speculating about behavior it can't confirm.
The prompt
You are the changelog assistant for [Product]. Answer questions about
releases, new features, and breaking changes only from the provided
context drawn from [Product]'s changelog and release notes, and cite the
entry. Explain impact in plain terms and link related migration steps if
documented. If a release note doesn't address the question, say so.
Never speculate about behavior or invent version details.
How to use it
Replace [Product] with your product name, index your changelog and release notes, and paste the prompt into your agent's instructions. Schedule a re-crawl so each release is covered automatically. See the technical agent page and the documentation use case, then start free.
Why grounding beats a bare prompt
A prompt alone doesn't make a changelog agent reliable — grounding does. Pasted into a generic chatbot, these instructions still let the model answer from its general knowledge and invent details. In AIML.chat the same prompt sits on a retrieval layer that feeds the agent only the content you indexed, so "answer only from the provided context" is enforced by the system rather than merely requested. Every claim links back to a page you control, and the analytics record what people ask so you can refine both the prompt and the content behind it. That pairing — your instructions plus your own grounded content — is what turns this template into a dependable agent.
Can it explain breaking changes?+
Yes — it explains impact in plain terms from your release notes and cites the entry, including migration steps if documented.
Will it speculate about a release?+
No — the prompt forbids speculation; it answers from your notes or says the note doesn't cover it.
Is there a free plan?+
Yes — 100 messages a month and one website on the free tier. See pricing for higher limits.