| name | skill-exercise-2 |
| description | Draft concise changelog entries from a provided list of merged pull requests, commit summaries, or issue titles. Use when the user asks for a short internal or customer-facing changelog and provides the source changes directly. |
Skill Exercise 2
This exercise skill exists for course inspection.
Use this skill to turn a small set of provided changes into a clear changelog. Do not inspect the
repository unless the user asks; rely on the source changes they provide.
Workflow
- Identify the intended audience: customer-facing, internal, or engineering.
- Group related changes into
Added, Changed, Fixed, and Removed only when those categories
are useful for the provided changes.
- Rewrite implementation-heavy details into user-visible outcomes.
- Preserve important warnings, migration notes, and compatibility details from the source material.
- Keep the final changelog brief enough to scan.
- Before finalizing, check each bullet against the source changes and remove anything unsupported.
Style
- Use plain language.
- Prefer specific nouns over vague claims like "improved experience".
- Do not invent impact, metrics, customer names, or roadmap intent.
- Mention uncertainty when the source material is ambiguous.
- Default to customer-facing language unless the user asks for an internal or engineering changelog.
Output
Use this structure, omitting empty sections:
# Changelog
## Added
- ...
## Changed
- ...
## Fixed
- ...
## Removed
- ...
## Notes
- ...
Add Notes only when the source material includes warnings, migrations, or follow-up work.
