app-store-release
Skill150 starsChanged 3 days agoMITView on GitHub
Release the latest lpm Link iOS build on App Store Connect (appstoreconnect.apple.com) through Chrome: first suggest the What's New text for the user's OK, then upload a build with mobile/ios/deploy.sh when needed, add the new version, attach the newest build, save What's New, refresh the screenshots (app-store-screenshots) and review video (app-review-video) when they're stale, then submit for review. Use when the user asks to release, ship or submit lpm Link / the iOS app to the App Store.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- mattblr/skillstheir own version, first seen Nov 8, 2026
- deonmenezes/mobile-app-skilltheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- deonmenezes/mobile-app-skill★ 4same name
- mattblr/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- mobile/AGENTS.mdAGENTS.md
- website/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- mobile/CLAUDE.mdCLAUDE.md
- website/CLAUDE.mdCLAUDE.md
- android-cliSkill
- app-review-videoSkill
- app-store-screenshotsSkill
- edge-to-edgeSkill
- lesson-publishSkill
- lessonSkill
- navigation-3Skill
- short-dailySkill
- short-gameSkill
- short-publishSkill
- short-raceSkill
- shortSkill
- lpm-cliSkill
- lpm-configSkill
- lpm-memorySkill
- lpmSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
What's New first: Before opening Chrome or uploading anything, draft the release notes:
- Distinctive: line 15
Write 3–6 short bullets of user-visible changes with no commit jargon and no mention of Tailscale.
- Very specific: line 22
Screenshots: If the screens changed or the user passed --screenshots, run the app-store-screenshots skill and upload the images as its …
- Distinctive: line 24
Submit: Ask for the user's OK, then click Add for Review → Submit to App Review.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What's New first. Before opening Chrome or uploading anything, draft the release notes:
- Live version:
curl -s 'https://itunes.apple.com/lookup?bundleId=cx.lpm.mobile'→results[0].version. The lookup can lag a few hours after a release; if App Store Connect later shows a newer live version, redraft. - The commit that set it:
git log --reverse --format=%h -S'MARKETING_VERSION: "<live>"' -- '*project.yml' | head -1(the*matters:project.ymlmoved frommobile/tomobile/ios/). - Changes since then:
git log --oneline <commit>..HEAD -- mobile ':!mobile/android' ':!mobile/parity'.
Write 3–6 short bullets of user-visible changes with no commit jargon and no mention of Tailscale. Show them to the user and wait for their OK or edits before going on.
- Live version:
Then use Claude in Chrome on the user's logged-in Chrome, starting at https://appstoreconnect.apple.com/apps → lpm Link.
- Build. Open TestFlight and find the newest build. If it isn't from the current
mobile/ioscode, or the user passed--upload, runmobile/ios/deploy.sh. It bumpsMARKETING_VERSIONinproject.yml(tell the user to commit that change), archives the app and uploads it. Reload until the build is no longer Processing, which takes about 5–15 minutes. - Version. On the Distribution tab, click + next to iOS App and enter the build's version. If a draft version already exists, use it instead.
- What's New. Paste the text the user approved in step 1. If new user-visible commits landed since the draft, show the extra bullets first.
- Screenshots. If the screens changed or the user passed
--screenshots, run theapp-store-screenshotsskill and upload the images as its "After a run" step says. Otherwise keep the screenshots from the previous version. - Build + review info. In the Build section, pick the build from step 2. If pairing or the main flows changed or the user passed
--video, runapp-review-videoand update App Review Information → Notes with the new version, build and video link. Keep Release set to the user's earlier choice. Leave everything else as it was. - Submit. Ask for the user's OK, then click Add for Review → Submit to App Review. Confirm the status reads "Waiting for Review". Report the version, build, What's New text and status.
Traps: ITSAppUsesNonExemptEncryption is false, so no export compliance question should come up. If one does, ask the user. Never press Release or change pricing or availability without the user's explicit request.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

