| name | changelog-release-tracker |
| description | Generate or update the internal OpenWork release changelog tracker as plain markdown release sections.
Triggers when user mentions:
- "generate changelog markdown"
- "track this release"
- "add a changelog entry"
|
Purpose
Use this skill to add or update the OpenWork release tracker using release history from _repos/openwork.
The tracker is split into files named release-tracker-{YYYY-MM-DD}.md in _repos/openwork/changelog/, where the date is the first release date in that file; append to the latest file, or create a new one (dated today) when the latest file already has 25 entries.
Output Contract
- The output file must be plain markdown sections.
- Keep release sections sorted oldest to newest so new versions append at the end.
- If the tracker file already exists, preserve its formatting and append or edit
## <version> sections in place.
- Each subsection inside a release must start and use a
#### heading.
- Use plain text under scalar subsections unless a subsection explicitly allows multiple markdown structures.
- Include a lines-of-code subsection and a release-importance subsection for every release.
- Include a
Title subsection for every release.
- The
Title must be concise, publish-ready, and reusable almost verbatim in the public changelog.
- The
Title, One-line summary, and Main changes must complement each other instead of repeating the same wording at different lengths.
Main changes may use the best-fit markdown structure described below instead of a fixed bullet count.
Inputs
- One or more release tags such as
v0.11.101
