app-store-google-play-optimice-and-resubmit-autonomously-skill

Installation
SKILL.md

App Store and Google Play Optimization and Resubmission

Carry the requested app through its actual review submission. Recover the original requirements and current provider records, implement every missing in-scope change, align the listing and reviewer information, and verify the exact submitted binary. When the request covers several apps or a numbered proposal set, cover the complete population.

Establish the target and current truth

  • Bind the repository, branch, source revision, developer account, app identifier, bundle ID or Android package, platform, version, build number or versionCode, target track, countries, localizations, and requested outcome. Resolve the provider mapping from its current record before mutations. A matching display name is insufficient.
  • Read local instructions, release tools, signing/export configuration and relevant history. Compare earlier completion claims against the actual code and current store records. Preserve unrelated dirty work and one submission owner per app.
  • Recover current rejection messages in full, including follow-up replies and attachments, from App Store Connect App Review or Play Console Policy status and the connected mailbox. Read the provider conversation even when an API state already says rejected. Messages may be unavailable through a public API. Use native mail tools or IMAP for email.
  • For each issue, retain the exact guideline or policy, reviewer observation, affected candidate, required evidence, owning source or metadata field, action and provider readback in the runtime task ledger. Keep this transient ledger out of the repository unless requested.
  • Read the full discoverable requirement set before classifying it. Numbered proposals marked complete still require code inspection through their normal entry points, persistence, lifecycle, accessibility and localization paths. Recount against the complete set after fixes.
  • Check current official documentation for the installed SDK, API and store policy before unfamiliar calls or a material route change. Reuse a working repository integration instead of inventing another service or wrapper.
  • Distinguish uploaded, processed, selected, submitted, waiting, in review, approved, released, available and purchased. Report the provider state that was actually read. A CI badge, successful upload, agent summary, TestFlight readiness email or release draft does not establish review submission.

Recover relevant prior work

When release history or earlier attempts change the action, use available conversation history and Chronicle to reconstruct recent cross-app and CLI work. Read the current Chronicle skill at ~/.codex/skills/chronicle/SKILL.md, its instructions at ~/.codex/memories_extensions/chronicle/instructions.md and relevant ~/.codex/memories_extensions/chronicle/resources/*.md when present. Screenpipe can locate a decisive previous review message or release action through ~/.codex/screenpipe-memories.md and its currently exposed search tools. Record actual source coverage in the runtime ledger. Historical artifacts are evidence. Verify the underlying current source or provider record before acting.

Read App Store Connect and Google Play

Installs
2
First Seen
8 days ago