The project follows Keep a Changelog and Semantic Versioning, with CHANGELOG.md kept in sync with plugin.json/marketplace.json versions. A small skill could automate adding a well-formed entry (Added/Changed/Fixed) after a change, reducing the chance the changelog goes stale.
Task (first pass): Propose the skill under `craftsman-plugin/skills/changelog-entry/` with:
- `SKILL.md` frontmatter + body in the style of the existing skills.
- The workflow: infer the change type, write the entry under the current unreleased/next version, match the existing CHANGELOG formatting.
Good first issue because: scoped to one new skill directory; the existing skills and CHANGELOG.md give a clear pattern to follow.
The project follows Keep a Changelog and Semantic Versioning, with CHANGELOG.md kept in sync with plugin.json/marketplace.json versions. A small skill could automate adding a well-formed entry (Added/Changed/Fixed) after a change, reducing the chance the changelog goes stale.
Task (first pass): Propose the skill under `craftsman-plugin/skills/changelog-entry/` with:
Good first issue because: scoped to one new skill directory; the existing skills and CHANGELOG.md give a clear pattern to follow.