Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.
Run scripts/collect_release_changes.sh from the repo root to gather commits and touched files. If needed, pass a specific tag or ref: scripts/collect_release_changes.sh v1.2.3 HEAD. If no tags exist, the script falls back to full history.
Scan commits and files to identify user-visible changes. Group changes by theme (New, Improved, Fixed) and deduplicate overlaps. Drop internal-only work (build scripts, refactors, dependency bumps, CI).
Write short, benefit-focused bullets for each user-facing change. Use clear verbs and plain language; avoid internal jargon. Prefer 5 to 10 bullets unless the user requests a different length.
Ensure every bullet maps back to a real change in the range. Check for duplicates and overly technical wording. Ask for clarification if any change is ambiguous or possibly internal-only.
Title (optional): "Whatβs New" or product name + version. Bullet list only; one sentence per bullet. Stick to storefront limits if the user provides one.
scripts/collect_release_changes.sh: Collect commits and touched files since last tag. references/release-notes-guidelines.md: Language, filtering, and QA rules for App Store notes.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.