skillshare changelog

Other Community

Skill notes

Step 3: Categorize Changes

Group commits by conventional commit type: Prefix · Category feat · New Features fix · Bug Fixes refactor · Refactoring

Step 4: Read Existing Entries for Style Reference

Before writing, read the most recent 2-3 entries in CHANGELOG.md to match the established tone and structure. The style evolves over time — always match the latest entries, not a hardcoded template.

Step 5: Write User-Facing Entry

Write from the user's perspective. Only include changes users will notice or care about. Include: New features with usage examples (CLI commands, code blocks) Bug fixes that affected user-visible behavior Breaking changes (renames, removed flags, scope changes)

Step 6: Update CHANGELOG.md

Read existing CHANGELOG.md and insert new entry at the top, after the header. Match the style of the most recent entries exactly. Structural conventions (based on actual entries): skillshare command --flag # usage example Key style points: Version numbers use [X.Y.Z] without v prefix in the heading

Step 7: Sync Website Changelog

The website has its own changelog page at website/src/pages/changelog.md. After updating CHANGELOG.md, sync the new entry to the website version. Differences between the two files: Website file has MDX frontmatter (title, description) and an intro paragraph — preserve these, don't overwrite Website file has a --- separator after the intro, before the first version entry The release entries themselves are identical in content

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@JetBrains · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Determine Version Range

Step 1: Determine Version Range

02
Step 2: Collect Commits

Step 2: Collect Commits

03
Step 3: Categorize Changes

Group commits by conventional commit type: Prefix · Category `feat` · New Features `fix` · Bug Fixes `refactor` · Refactoring

04
Step 4: Read Existing Entries for Style Reference

Before writing, read the most recent 2-3 entries in `CHANGELOG.md` to match the established tone and structure. The style evolves over time — always match the latest entries, not a hardcoded template.

05
Step 5: Write User-Facing Entry

Write from the user's perspective. Only include changes users will notice or care about. Include: New features with usage examples (CLI commands, code blocks) Bug fixes that affected user-visible behavior Breaking changes (renames, removed flags, scope changes)

06
Step 6: Update CHANGELOG.md

Read existing `CHANGELOG.md` and insert new entry at the top, after the header. Match the style of the most recent entries exactly. Structural conventions (based on actual entries): skillshare command --flag # usage example Key style points: Version numbers use `[X.Y.Z]` without `v` prefix in the heading

07
Step 7: Sync Website Changelog

The website has its own changelog page at `website/src/pages/changelog.md`. After updating `CHANGELOG.md`, sync the new entry to the website version. Differences between the two files: Website file has MDX frontmatter (`title`, `description`) and an intro paragraph — preserve these, don't overwrite Website file has a `---` separator after the intro, before the first version entry The release entries themselves are identical in content

08
Step 8: RELEASENOTES (Maintainer Only)

`specs/RELEASE_NOTES_<version>.md` is only generated when the user is the project maintainer (runkids). Contributors skip this step. Check if running as maintainer: If maintainer: Read the most recent `specs/RELEASE_NOTES_*.md` as a style reference Generate `specs/RELEASE_NOTES_<version>.md` (no `v` prefix, e.g. `RELEASE_NOTES_0.17.6.md`)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.