Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Lm655hdgDo5xsSLNomgdsy
23 lines
858 B
Plaintext
23 lines
858 B
Plaintext
# Loading one skill: two model calls
|
|
|
|
model calls: 2
|
|
first call mentions the skill body ('Breaking' in any message) : false
|
|
|
|
--- tool result fed back to the model (what the Skill tool returned) ---
|
|
Base directory for this skill: <module>/target/classes/skills/release-notes
|
|
|
|
# Release notes
|
|
|
|
Turn a list of merged changes into release notes a user can act on.
|
|
|
|
1. Group the changes under **Breaking**, **Added**, **Fixed** and **Internal**, in that order.
|
|
2. Lead every **Breaking** item with what the reader must change, not with what the team did.
|
|
3. Read `references/style-guide.md` (in this skill's directory) before writing the final text.
|
|
4. Never invent a ticket number. If a change has none, leave the reference out.
|
|
|
|
Return the notes as Markdown with one bullet per change.
|
|
|
|
--- final answer ---
|
|
## Breaking
|
|
- Rename `cache.ttl` to `cache.expiry`.
|