skillshare-release
- Repo stars 1,897
- Author updated Live
- Author repo skillshare
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skillshare-release
description: >- End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., v0.19.0).…
category: other
runtime: no special runtime
---
# skillshare-release output preview
## PART A: Task fit
- Use case: >- End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., v0.19.0). Run full test suite and code quality checks. Fix any failures before proceeding. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Prerequisites / Workflow / Phase 1: Validate” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “>- End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., v0.19.0). Run full test suite and code quality checks. Fix any failures before proceeding. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Prerequisites / Workflow / Phase 1: Validate” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/changelog`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Prerequisites / Workflow / Phase 1: Validate”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skillshare-release
description: >- End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., v0.19.0).…
category: other
source: runkids/skillshare
---
# skillshare-release
## When to use
- >- End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., v0.19.0). Run full test suite a…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Prerequisites / Workflow / Phase 1: Validate” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skillshare-release" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Prerequisites / Workflow / Phase 1: Validate
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., v0.19.0).
Prerequisites
- All feature work merged to current branch
- Working directory clean (
git statusshows no uncommitted changes)
Workflow
Phase 1: Validate
Run full test suite and code quality checks. Fix any failures before proceeding.
make check # fmt-check + lint + test (builds binary first)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
- Syncing website changelog (
website/src/pages/changelog.md)
Review the output before proceeding.
Phase 3: Release Notes (Maintainer Only)
Check if running as maintainer:
git config user.name # Should match "Willie" or maintainer identityIf 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 - TL;DR section with numbered highlights
- One
##section per feature/fix — describe what changed in plain language, with a CLI example or code block if relevant - Include migration guide if breaking changes exist
Wording rules (same user-facing standard as CHANGELOG):
- Describe what changed from the user's perspective, not how the code changed
- Never mention: function names, variable names, struct fields, file paths, Go syntax, internal APIs
- ✅ Good: "Sync now auto-creates missing target directories and shows what it did"
- ❌ Bad: "upgraded
Server.mufromsync.Mutextosync.RWMutexand applied a snapshot pattern across 30 handlers" - Keep it concise — a short paragraph per feature is enough
If not maintainer: Skip this phase.
Phase 4: Version Bump
Update the version in skills/skillshare/SKILL.md frontmatter:
metadata:
version: vX.Y.ZThis ensures skillshare upgrade --skill detects the new version correctly.
Phase 5: Commit & Tag
git add -A
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.ZDo NOT push yet — wait for user confirmation.
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.
Phase 7: Present & Confirm
Show the user:
- Test results (pass/fail)
- CHANGELOG.md diff
- RELEASE_NOTES file (if generated)
- Version bump diff
- GitHub release draft
- Social media draft
Wait for user approval before pushing:
git push origin HEAD --tagsRules
- Fix, don't skip — if tests fail, fix them before continuing
- User perspective — all written output is for users, not developers
- Short drafts — announcements default to concise; user will ask for more detail if needed
- No fabricated links — never invent URLs or references
- Verify before claiming — grep source before stating a feature exists
- Ask before push — never push or publish without explicit user confirmation
- Commit message — always
chore: release vX.Y.Z - No competitive references — never mention competitor repos in commit messages or notes
Decide Fit First
Design Intent
How To Use It
Boundaries And Review