App Store Changelog

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 ask...

Security Scan

The skill's instructions, files, and single helper script are consistent with its stated purpose (building App Store release notes from git history) and do not request unrelated credentials or installs.

Purpose & Capability

Name and description match the actual artifacts: SKILL.md and a small shell script that collect git commits and touched files. No extraneous env vars, binaries, or network endpoints are requested.

Instruction Scope

SKILL.md confines runtime actions to running the included script and summarizing its output. It does rely on agent judgment to triage user-impacting changes (which is appropriate) and may lead the agent to inspect repo content or commit messages — expected for this task but worth noting since repo data can contain sensitive paths/messages.

Install Mechanism

No install spec; this is instruction-only with a tiny included script. Nothing is downloaded or written to disk by an installer.

Credentials

The skill declares no environment variables, credentials, or config paths. The script uses only local git; no external secrets are requested.

Persistence & Privilege

always:false and no special privileges or persistent system changes. The skill does not alter other skills or system-wide settings.

Assessment

This skill appears coherent and limited in scope, but review these practical points before installing: (1) it runs git commands and prints repo root, commit summaries, and file paths — only use it on repositories you trust because commit messages or paths can include sensitive info; (2) the agent will need to interpret commit messages and touched files to decide what is 'user-facing' — ask for clarification when ambiguous; (3) there are no network calls or credential requests in the provided files, but if the skill is later modified to call external services, re-check for unexpected endpoints; (4) you can safely inspect or run scripts/collect_release_changes.sh locally to see exactly what it prints before giving the agent access.

📖 Complete setup guide: https://skillboss.co/skill.md

Overview

Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.

Workflow

1) Collect changes

• 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.

2) Triage for user impact

• 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).

3) Draft App Store notes

• 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.

4) Validate

• 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.

Output Format

• 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.

Resources

• 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.