release-prep
Pre-release checklist: version bump, changelog, privacy manifest, store metadata, archive readiness. Triggers: "release prep", "prepare release", "ready to ship", "pre-release checklist".
Terry Nyberg · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Terryc21/sitrep --skill release-prepAbout this skill
name: release-prep description: 'Pre-release checklist: version bump, changelog, privacy manifest, store metadata, archive readiness. Triggers: "release prep", "prepare release", "ready to ship", "pre-release checklist".' version: 2.1.0 author: Terry Nyberg license: Apache-2.0 allowed-tools: [Read, Grep, Glob, Bash, Edit, Write, AskUserQuestion] metadata: tier: execution category: release
Release Prep
Quick Ref: Automated pre-release checklist: version bump, changelog, privacy check, store metadata, archive. Output:
.agents/research/YYYY-MM-DD-release-prep-vX.Y.Z.md
YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
Pre-flight: Git Safety Check
git status --short
If uncommitted changes exist:
AskUserQuestion with questions:
[
{
"question": "You have uncommitted changes. Commit before proceeding?",
"header": "Git",
"options": [
{"label": "Commit first (Recommended)", "description": "Save current work so you can revert if this skill modifies files"},
{"label": "Continue without committing", "description": "Proceed — I accept the risk"}
],
"multiSelect": false
}
]
If "Commit first": Ask for a commit message, stage changed files, and commit. Then proceed.
Step 1: Determine Release Details
AskUserQuestion with questions:
[
{
"question": "What type of release is this?",
"header": "Release type",
"options": [
{"label": "Patch (X.Y.Z+1)", "description": "Bug fixes only, no new features"},
{"label": "Minor (X.Y+1.0)", "description": "New features, backwards compatible"},
{"label": "Major (X+1.0.0)", "description": "Breaking changes or major milestone"},
{"label": "Hotfix", "description": "Urgent production fix"}
],
"multiSelect": false
}
]
Step 2: Find Current Version
2.1: Locate Version in Project
# Find MARKETING_VERSION in pbxproj
Grep pattern="MARKETING_VERSION" glob="**/*.pbxproj" output_mode="content"
# Find CURRENT_PROJECT_VERSION (build number)
Grep pattern="CURRENT_PROJECT_VERSION" glob="**/*.pbxproj" output_mode="content"
# Check for version in Info.plist (older projects)
Grep pattern="CFBundleShortVersionString|CFBundleVersion" glob="**/*.plist" output_mode="content"
2.2: Check Last Git Tag
# Get the most recent version tag
git tag --sort=-v:refname | head -5
# Get the most recent tag with its date
git log --tags --simplify-by-decoration --format="%ai %d" | head -5
2.3: Calculate New Version
Based on release type and current version:
| Current | Patch | Minor | Major |
|---|---|---|---|
| 1.2.3 | 1.2.4 | 1.3.0 | 2.0.0 |
Record:
- Current version: X.Y.Z → New version: X.Y.Z
- Current build: N → New build: N+1
Step 3: Bump Version Numbers
3.1: Update MARKETING_VERSION
# Find the exact line in pbxproj
Grep pattern="MARKETING_VERSION = " glob="**/*.pbxproj" output_mode="content"
# Edit each occurrence (there may be multiple — one per build configuration)
# Use Edit with replace_all=true
3.2: Update CURRENT_PROJECT_VERSION
# Same approach — find and replace all occurrences
Grep pattern="CURRENT_PROJECT_VERSION = " glob="**/*.pbxproj" output_mode="content"
3.3: Verify
# Confirm versions updated correctly
Grep pattern="MARKETING_VERSION|CURRENT_PROJECT_VERSION" glob="**/*.pbxproj" output_mode="content"
Step 4: Generate Changelog
4.1: Get Commits Since Last Release
# Commits since last tag, one per line
git log <last_tag>..HEAD --oneline --no-merges
# If no tags exist, use a date range
git log --since="2026-01-01" --oneline --no-merges
4.2: Categorize Changes
Sort commits into categories:
## What's New in [version]
### Features
- [New capabilities added]
### Improvements
- [Enhancements to existing features]
### Bug Fixes
- [Issues resolved]
### Under the Hood
- [Technical changes users don't directly see]
4.3: Write App Store "What's New" Text
Draft user-facing release notes (max 4000 characters):
- Lead with the most impactful change
- Use plain language (no technical jargon)
- 3-8 bullet points is ideal
Step 5: Code Readiness Check
5.1: Test Status
Ask the user before running tests (they may take a while or require specific configuration):
AskUserQuestion with questions:
[
{
"question": "Should I run the test suite now?",
"header": "Tests",
"options": [
{"label": "Yes, run tests", "description": "Run xcodebuild test (may take a few minutes)"},
{"label": "Skip tests", "description": "I'll run tests separately or they've already passed"},
{"label": "Check last results", "description": "Just check the most recent test outcome"}
],
"multiSelect": false
}
]
If running tests, determine the scheme and simulator:
# Find available schemes
xcodebuild -list -json 2>/dev/null | head -30
# Run tests — adjust scheme and destination for the project
xcodebuild test -scheme <AppName> -destination 'platform=iOS Simulator,name=iPhone 16' -quiet 2>&1 | tail -10
5.2: Check for Debug Code Left Behind
# Pass 1: Find all debug prints
Grep pattern="print\(|NSLog\(|debugPrint\(" glob="**/*.swift" output_mode="files_with_matches"
# Pass 2: For each flagged file, read it and check if prints are inside #if DEBUG
# Prints inside #if DEBUG blocks are SAFE — they're stripped from release builds
# Only report prints that are NOT behind #if DEBUG as issues
# Find TODO/FIXME that might be release blockers
# NOTE: not all TODOs are blockers — read each to assess urgency
Grep pattern="(TODO|FIXME|HACK|XXX):" glob="**/*.swift" output_mode="content"
# Find hardcoded test data
Grep pattern="localhost|127\\.0\\.0\\.1|test@|example\\.com" glob="**/*.swift" output_mode="content"
5.3: Check for Warnings
# Build and count warnings — adjust sche
Read the complete source ↗