app-store-changelog

Included with Lifetime

$97 forever

Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags.

General

What this skill does


# App Store Changelog

## Overview

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

## Workflow

### 1) Collect Changes

Get commits since the last tag:

```bash
# Find the last tag
git describe --tags --abbrev=0

# List commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline

# Or with more detail
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"%h %s" --no-merges
```

If comparing specific refs:
```bash
git log v1.2.3..HEAD --oneline --no-merges
```

If no tags exist:
```bash
git log --oneline --no-merges -50  # Last 50 commits
```

### 2) Triage for User Impact

Scan commits and identify user-visible changes:

**Include:**
- New features
- UI changes
- Behavior changes
- Bug fixes users would notice
- Performance improvements with visible impact

**Exclude:**
- Refactors
- Dependency bumps
- CI changes
- Developer tooling
- Internal logging
- Analytics changes (unless affecting user privacy/behavior)

Group changes by theme:
- **New**: New features and capabilities
- **Improved**: Enhancements to existing features
- **Fixed**: Bug fixes

### 3) Draft App Store Notes

Write short, benefit-focused bullets:

- Use clear verbs and plain language
- Avoid internal jargon, ticket IDs, file paths
- Prefer 5-10 bullets unless user specifies different length
- Each bullet: one sentence, starts with a verb

**Language guidance:**
- Translate technical terms to user-facing descriptions
- Avoid: "API", "refactor", "nil", "crash log", "dependency"
- Use: "Improved", "Added", "Fixed", "Updated"
- Keep tense consistent (present or past)

**Examples:**
- "Added account switching from the profile menu."
- "Improved timeline loading speed on slow connections."
- "Fixed media attachments not opening in full screen."

### 4) Validate

- [ ] Every bullet maps to a real change in the range
- [ ] No duplicate bullets describing the same change
- [ ] No internal jargon or file paths
- [ ] Final list fits App Store text limits (if provided)

## Output Format

```
What's New

• Added [feature description]
• Improved [enhancement description]
• Fixed [bug fix description]
```

Or with sections:

```
What's New in [Version]

New
• [Feature 1]
• [Feature 2]

Improved
• [Enhancement 1]

Fixed
• [Bug fix 1]
• [Bug fix 2]
```

## Quick Commands

```bash
# Full workflow: commits since last tag with files changed
git log $(git describe --tags --abbrev=0)..HEAD --stat --no-merges

# Just commit messages
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"- %s" --no-merges

# List all tags
git tag -l --sort=-v:refname

# Compare two specific tags
git log v1.1.0..v1.2.0 --oneline --no-merges
```

## Tips

- If a change is ambiguous, ask for clarification
- Drop changes that are clearly internal-only
- When in doubt, describe as "small improvement" only if user-visible
- Respect storefront character limits if provided

Files: 1

Size: 3.1 KB

Complexity: 6/100

Category: General

Source: https://github.com/jclfocused/claude-agents/tree/main/skills/release-app-store-changelog

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts