skillshare release

Other Community

Skill notes

Prerequisites

All feature work merged to current branch Working directory clean (git status shows no uncommitted changes)

Phase 1: Validate

Run full test suite and code quality checks. Fix any failures before proceeding. If tests fail: fix them, don't skip. Do not ask the user — fix and re-run.

Phase 2: Changelog

Invoke /changelog $VERSION to generate the changelog entry. This handles: Collecting commits since last tag Categorizing by conventional commit type Writing user-facing CHANGELOG.md entry

Phase 3: Release Notes (Maintainer Only)

Check if running as maintainer: If maintainer: Read the most recent specs/RELEASE_NOTES_*.md as a style reference, then generate specs/RELEASE_NOTES_<version>.md (no v prefix, e.g., RELEASE_NOTES_0.19.0.md). Structure: Title: # skillshare vX.Y.Z Release Notes

Phase 4: Version Bump

Update the version in skills/skillshare/SKILL.md frontmatter: This ensures skillshare upgrade --skill detects the new version correctly.

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
@runkids · 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
Phase 1: Validate

Run full test suite and code quality checks. Fix any failures before proceeding. If tests fail: fix them, don't skip. Do not ask the user — fix and re-run.

02
Phase 2: Changelog

Invoke `/changelog $VERSION` to generate the changelog entry. This handles: Collecting commits since last tag Categorizing by conventional commit type Writing user-facing CHANGELOG.md entry

03
Phase 3: Release Notes (Maintainer Only)

Check if running as maintainer: If maintainer: Read the most recent `specs/RELEASE_NOTES_*.md` as a style reference, then generate `specs/RELEASE_NOTES_<version>.md` (no `v` prefix, e.g., `RELEASE_NOTES_0.19.0.md`). Structure: Title: `# skillshare vX.Y.Z Release Notes`

04
Phase 4: Version Bump

Update the version in `skills/skillshare/SKILL.md` frontmatter: This ensures `skillshare upgrade --skill` detects the new version correctly.

05
Phase 5: Commit & Tag

Do NOT push yet — wait for user confirmation.

06
Phase 6: Draft Announcements

Prepare two drafts for user review: GitHub Release Notes — concise, user-facing summary suitable for the GitHub release page. Shorter than RELEASE_NOTES, highlight top 3-5 changes with one-liners. Social media post — 2-3 sentences max, casual tone, mention the version and 1-2 headline features. No hashtag spam. Tone: short, direct. Don't oversell. The user will edit before posting.

07
Phase 7: Present & Confirm

Show the user: [ ] Test results (pass/fail) [ ] CHANGELOG.md diff [ ] RELEASE_NOTES file (if generated) [ ] Version bump diff

Discussion

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