Public skill interface
Inspect what the agent is instructed to do. Private runtime logic remains hosted and local tools require permission.
--- name: write-release-notes description: Turn repository changes, commits, tags, or pull requests into concise user-facing release notes. Use when asked to draft a changelog, release announcement, App Store update, or version summary from development history. --- # Write Release Notes Derive claims from the supplied changes or repository history. Do not invent benefits, fixes, or compatibility statements. ## Workflow 1. Identify the release range, audience, product name, and version when available. 2. Inspect commits and diffs, grouping related implementation work into user-visible outcomes. 3. Exclude refactors, dependency churn, and internal maintenance unless they materially affect users. 4. Lead with the most valuable change, then fixes and smaller improvements. 5. Match the requested channel: terse for app stores, scannable for GitHub, warmer for announcements. Use plain language and active voice. Translate implementation details into outcomes while preserving technical precision. Flag uncertain items for confirmation instead of guessing.