Skip to content
Agentmart
Submit a tool

solo-ios-release-flow

Use when coordinating the end-to-end release sequence for a prepared SwiftUI app, from final verification through TestFlight or App Store submission.

Skill by phrypy

IndexedMIT★ 7
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/phrypy-solo-ios-release-flow

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when coordinating the end-to-end release sequence for a prepared SwiftUI app, from final verification through TestFlight or App Store submission.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/solo-ios-release-flow

What's inside

Skill name
solo-ios-release-flow
Description
Use when coordinating the end-to-end release sequence for a prepared SwiftUI app, from final verification through TestFlight or App Store submission.
License
MIT
Instructions
46 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Solo iOS Release Flow

Ship with a repeatable loop. Do not improvise the final mile.

## Recommended Sequence

1. clean up real warnings
2. run the relevant tests
3. build the app in release conditions
4. smoke test the main user flows
5. run `app-store-readiness`
6. archive and upload
7. check processing, screenshots, and review notes

Run `app-store-readiness` before the upload step. That skill is the go/no-go audit; this skill owns the order of operations. Use `ship-ios-build-one-command` only for the archive, sign, export, and upload step.

## Before You Upload

- remove debug-only behavior
- confirm version and build numbers
- hand App Store metadata, privacy, capability, and reviewer-risk checks to `app-store-readiness`

## Solo Builder Priorities

- stability beats extra features
- reduce ambiguity in settings, paywalls, and sync
- do one final pass on first-run experience
- keep release notes tight and honest

## Go / No-Go Questions

- can a new user understand the core loop
- can a paying user understand what they are buying
- can a reviewer reach the important surfaces without confusion
- does the app promise only what the build actually does

If any answer is no, stop and fix that first.

## After Upload

- watch build processing
- re-check metadata in App Store Connect
- prepare concise review notes when needed
- keep one short list of post-submit follow-ups instead of thrashing the release

From phrypy/ios-app-playbook, MIT.

More from phrypy/ios-app-playbook

Signals

Stars
7
Forks
2
Open issues
0
Last commit (this folder)
Jun 23, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from phrypy

Cite this page

solo-ios-release-flow skill. Agent Mart. https://agentmart.dev/skills/phrypy-solo-ios-release-flow (last updated 2026-10-24)