Skip to content

docs: strengthen changelog release tracker guidance#30

Open
jcllobet wants to merge 1 commit intomainfrom
task/improve-changelog-skill
Open

docs: strengthen changelog release tracker guidance#30
jcllobet wants to merge 1 commit intomainfrom
task/improve-changelog-skill

Conversation

@jcllobet
Copy link
Copy Markdown
Contributor

@jcllobet jcllobet commented Apr 5, 2026

Summary

  • add a required publish-ready Title field to the release tracker skill and make it distinct from the one-line summary and main changes
  • align the skill's writing guidance with stronger public changelog patterns by emphasizing outcome-first, user-facing, and developer-friendly language
  • update the output contract, full example block, publication verification rules, and validation checklist so tracker entries map more cleanly into packages/docs/changelog.mdx

Test plan

  • git diff --check -- .opencode/skills/changelog-release-tracker/SKILL.md
  • ReadLints on .opencode/skills/changelog-release-tracker/SKILL.md
  • Baseline pressure test of the original skill against recent changelog entries
  • Post-edit pressure test of the revised skill against recent changelog entries
  • Final review pass on the updated skill guidance

Made with Cursor

Add a publish-ready Title field and tighten the tracker writing rules so internal release entries map more cleanly into OpenWork's public changelog voice.

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant