create-ios-release

A set of rules for releasing an iOS app, Apple's mobile operating system, to the App Store.

In plain words
What is it for?
It helps prepare app versions, increment build numbers, tag releases in Git, and guide the submission process.
Why use it?
It reduces release mistakes by organizing version numbers, build numbers, Git tags, and release notes.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/brunogama/ios-cursor-rules/create-ios-release
Clone the repo
git clone --depth 1 https://github.com/brunogama/ios-cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,440 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02440
Opus 5 $0.00000 $0.01220
Sonnet 5 $0.00000 $0.00488
Haiku 4.5 $0.00000 $0.00244

Measured yesterday against content hash 301ad881814d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-ios-release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/create-ios-release.mdc · 386 lines

How it starts

The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.

iOS App Release Process

As an AI assistant helping with iOS app releases, I should guide through the following process for successfully deploying iOS applications to the App Store.

Versioning and Build Numbers

Version Numbering Scheme

  • Follow semantic versioning (MAJOR.MINOR.PATCH):
    • MAJOR: Breaking changes or significant UI redesigns
    • MINOR: New features with backward compatibility
    • PATCH: Bug fixes and minor improvements
  • Update the version number in Xcode project settings (Info.plist)
  • Increment build number for each submission, even for the same version
// Examining and updating Info.plist values programmatically
guard let infoPlistPath = Bundle.main.path(forResource: "Info", ofType: "plist"),
      let infoPlist = NSDictionary(contentsOfFile: infoPlistPath) as? [String: Any] else {
    return
}

let version = infoPlist["CFBundleShortVersionString"] as? String // Version number (e.g. "1.2.3")
let build = infoPlist["CFBundleVersion"] as? String // Build number (e.g. "42")

Git Tagging

  • Tag each release in Git with the version number
  • Use annotated tags with release notes
  • Consider using a prefix like 'v' (e.g., v1.2.0)
# Create an annotated tag
git tag -a v1.2.0 -m "Version 1.2.0: Added dark mode support and fixed login issues"

# Push tags to remote
git push origin v1.2.0

Code Signing and Provisioning

Certificate Management

  • Use Xcode's Automatic Code Signing when possible
  • For manual signing, ensure certificates are properly installed and maintained
  • Consider using cert/match tools from fastlane for team management
  • Keep track of certificate expiration dates to avoid crisis

Provisioning Profiles

  • Use appropriate profile types for different distribution methods:
    • Development: For testing on developer devices
    • Ad Hoc: For internal distribution to registered devices
    • App Store: For App Store and TestFlight distribution
  • Regenerate provisioning profiles when adding new devices or capabilities
  • Keep profiles organized and up to date

Read the full file on GitHub · 386 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 386 lines · 0 tokens per session scan A 301ad881814d

Subscribe to this mod's changes

create-ios-release is a cursor rule published in the GitHub repository brunogama/ios-cursor-rules (74 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,440 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.