⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
skillshare-changelog
>-
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
[!NOTE] Latest: v0.30.7 — Let accepted findings pass in CI:
skillshare audit --respect-acceptedno longer fails on findings you accepted with--forceduringinstallorupdate, the same way the update gate treats them. They stay in the report, marked as accepted. audit reference → · All releases →
Why skillshare
Switching AI tools should not mean rebuilding your setup. skillshare gives your skills and other AI resources a home you control.
- Switch tools, keep your skills — edit once, then sync to Claude Code, Codex, Pi and the other tools you use.
- Take your setup with you — version your source in Git and pull it onto another machine.
- Share with your team — keep project resources with your code and distribute shared skills through tracked repositories.
One teammate uses Claude Code, another uses Codex. Keep their shared code-review checklist in .skillshare/ alongside the project. New teammates install the declared skills and sync to the configured tools instead of copying instructions from chat. Team onboarding →
Use the desktop app or CLI to manage everything locally, audit skills before use, and choose what each tool receives.
Coming from another tool? Migration Guide · Comparison
CLI and UI Preview
| Skill Detail | Security Audit |
|---|---|
| UI Dashboard | UI Skills |
|---|---|
Installation
[!TIP] Use skillshare from your desktop. Get Skillshare App for macOS (Apple Silicon), Windows and Linux. First launch helps you install or locate the CLI, choose your AI tools and run your first sync. Installation guide.
Desktop App — visual setup and daily management
Skillshare App puts skills, agents, MCP and hooks in a desktop window. Install the app, open it, and follow first-launch setup.
macOS (Apple Silicon), with Homebrew:
brew tap runkids/tap
brew install --cask skillshare-app
Windows / Linux, or a manual macOS install: Download the latest app installers. See the Desktop App guide for platform details.
CLI: macOS / Linux
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh
The script installs to ~/.local/bin by default, so normal installs and updates do not need sudo. If the installer prints PATH setup instructions, follow them before running skillshare. Add the suggested line to your shell config (such as ~/.zshrc or ~/.bashrc) for future terminals. Set INSTALL_DIR to use another location.
Windows PowerShell
irm https://raw.githubusercontent.com/runkids/skillshare/main/install.ps1 | iex
CLI: Homebrew
brew install skillshare
Tip: Run
skillshare upgradeto update to the latest version. It auto-detects your install method and handles the rest.
CLI: Nix
nix profile add github:runkids/skillshare
Update with nix profile upgrade skillshare. Requires Nix 2.30+ with flakes enabled; on older Nix or Lix, use nix profile install. NixOS and Home Manager configurations can use the flake's overlays.default.
GitHub Actions
- uses: runkids/setup-skillshare@v1
with:
source: ./skills
- run: skillshare sync
See setup-skillshare for all options (audit, project mode, version pinning).
Shorthand (Optional)
Add an alias to your shell config (~/.zshrc or ~/.bashrc):
alias ss='skillshare'
Quick Start
skillshare init # Create config, source, and detected targets
skillshare sync # Sync skills to all targets
How It Works
- macOS / Linux:
~/.config/skillshare/ - Windows:
%AppData%\skillshare\
┌─────────────────────────────────────────────────────────────┐
│
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
.skillshare/skills/skillshare-changelog/SKILL.md6.1 KBb8692c04060dupstream ↗
--- name: skillshare-changelog description: >- Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog sync. For full release workflows (Release PR review, tests, draft assets, publication, announcements), use /release instead. argument-hint: "[tag-version]" metadata: targets: [claude, universal] --- Review or generate a user-facing changelog entry. Prefer the open Release Please PR and its manifest version for an upcoming release. For historical work, $ARGUMENTS specifies the requested tag or commit range. **Scope**: This skill updates `CHANGELOG.md` and syncs the website changelog (`website/src/pages/changelog.md`). It does NOT generate RELEASE_NOTES, choose a new version, or handle the full release workflow — use `/release` for that. Before acting, run `python3 scripts/ai-context.py release`. That topic is the source of truth for authorization, changelog content and synchronization rules; this skill retains the entry-generation workflow. ## Workflow ### Step 1: Determine Version Range For an upcoming release, work on the Release PR branch and read `.github/release-please-manifest.json`. Verify the latest published tag and use its range to the Release PR head. Keep the proposed version; this skill does not authorize a version change. Tags may exist for unpublished drafts, so do not assume the highest local tag is the latest published release. For historical work, use the user-requested tags or range. ### Step 2: Collect Commits ```bash git log <previous-published-tag>..<release-pr-head-or-requested-tag> --oneline --no-merges ``` Review the generated Release Please entry before writing. Preserve useful manual examples and migration notes. Do not add a second entry for the same version. ### Step 3: Categorize Changes Group commits by conventional commit type: | Prefix | Category | |--------|----------| | `feat` | New Features | | `fix` | Bug Fixes | | `perf` | Performance | | breaking change | Breaking Changes and migration notes | | `revert` | Reverts, when user-visible | Exclude test-only, CI-only, pure refactoring, documentation-only and internal maintenance entries from published notes. ### 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) - Performance improvements users would notice **Exclude**: - Internal test changes (smoke tests, test refactoring) - Implementation details (error propagation, internal structs) - Dev toolchain changes (Makefile cleanup, CI tweaks) - Pure documentation adjustments **Wording guidelines**: - Don't use "first-class", "recommended" for non-default options - Be factual: "Added X" / "Fixed Y" / "Renamed A to B" - Include CLI example when introducing a new feature - Use em-dash (`—`) to separate feature name from description - Group related features under `####` sub-headings when there are 2+ distinct areas ### Step 6: Update CHANGELOG.md Edit the existing generated entry on the Release PR branch. If the requested historical entry does not exist, insert it at the appropriate position. Match the style of the most recent entries. Structural conventions (based on actual entries): ```markdown ## [X.Y.Z] - YYYY-MM-DD ### New Features #### Feature Area Name - **Feature name** — description with `inline code` for commands and flags ```bash skillshare command --flag # usage example ``` Additional context as sub-bullets or continuation text #### Another Feature Area - **Feature name** — description ### Bug Fixes - Fixed specific user-visible behavior — with context on what changed - Fixed another issue ### Performance - **Improvement name** — description of what got faster ### Breaking Changes - Renamed `old-name` to `new-name` ``` Key style points: - Version numbers use `[X.Y.Z]` without `v` prefix in the heading - Feature bullets use `**bold name** — em-dash description` format - Code blocks use `bash` language tag for CLI examples - Bug fixes describe the symptom, not the implementation - Only include sections that have content (skip empty Performance, Breaking Changes, etc.) ### 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 For an upcoming Release PR, run inside the devcontainer: ```bash python3 scripts/release/release.py sync python3 scripts/release/release.py check ``` The helper normalizes the generated version heading, replaces or prepends only the newest website entry, and synchronizes the built-in skill metadata to the already proposed manifest version. It preserves website frontmatter, intro and historical entries. It does not choose or bump a version. For historical corrections, edit the matching entry in both files directly; the helper handles only the current manifest release. Review the diff and run `python3 scripts/ai-context.py check`. ## Rules Apply the `release` topic. This adapter is changelog-only and does not broaden authorization to commit, tag, push or publish.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/runkids-skillshare-skillshare-skills-skillshare-changelog.md