agentleFS
gug007gug007/lpm/.claude/skills/app-store-release/SKILL.md

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

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
  1. Distinctive:

    What's New first: Before opening Chrome or uploading anything, draft the release notes:

    line 10
  2. Distinctive:

    Write 3–6 short bullets of user-visible changes with no commit jargon and no mention of Tailscale.

    line 15
  3. Very specific:

    Screenshots: If the screens changed or the user passed --screenshots, run the app-store-screenshots skill and upload the images as its …

    line 22
  4. Distinctive:

    Submit: Ask for the user's OK, then click Add for Review → Submit to App Review.

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
  1. 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.yml moved from mobile/ to mobile/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.

Then use Claude in Chrome on the user's logged-in Chrome, starting at https://appstoreconnect.apple.com/apps → lpm Link.

  1. Build. Open TestFlight and find the newest build. If it isn't from the current mobile/ios code, or the user passed --upload, run mobile/ios/deploy.sh. It bumps MARKETING_VERSION in project.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.
  2. 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.
  3. 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.
  4. Screenshots. If the screens changed or the user passed --screenshots, run the app-store-screenshots skill and upload the images as its "After a run" step says. Otherwise keep the screenshots from the previous version.
  5. 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, run app-review-video and 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.
  6. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.