App Store Compliance Playbook skill
A guard hook before an App Store or Google Play submit finds critical rejection risks and blocks the command until they are fixed.
- 429 ★ on the repository
- Last commit
Extended access
Why this level
- The installer edits agent configs and registers a hook on submit commands.
- The hook blocks commands, so a false positive can stop a release.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/app-store-compliance-playbookDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The installer edits agent configs and registers a hook on submit commands.
- The hook blocks commands, so a false positive can stop a release.
This is third-party code. Review the repository files before installing.
What it does
The repository combines a reference of Apple App Store and Google Play rejection causes with the guard script `app-store-compliance-guard.sh`. The guard scans an iOS or Android project and prints a verdict: `BLOCKED.` for a critical risk, `CLEAR.` if none, or `NOT CHECKED.` when no project is found. Under each `[CRITICAL]` a `fix.` line gives the correction. The `scripts/install.sh` installer sets the guard as a hook before submit commands, such as an upload to App Store Connect, and adds a skill and the `/app-store-audit` command for Claude Code, Gemini CLI and OpenCode. Supported are Claude Code, Codex CLI, Gemini CLI, OpenCode, Cursor, Copilot, Grok, Qwen Code, Kimi Code, Factory Droid, Auggie and Windsurf.
Who it is for. Mobile developers who do not want to lose a week to a review rejection after submitting an app.
Good fit when
- Before an iOS app release the project should be checked for typical rejection causes.
- An agent is about to submit a build with `fastlane` or `eas submit` and the submission should stop on a critical finding.
- The app has already been rejected and the appeal steps from `docs/MISTAKE-PATTERNS.md` are needed.
- A team needs an account and regional deadline checklist before the first launch.
Not a fit when
- The app is not submitted to stores.
- Hooks on agent commands are forbidden by team policy.
- A legal opinion is required: the guard checks code, not contracts and accounts.
Example request
Check my project in `./MyApp` with the App Store Compliance guard, show findings by severity and explain the fixes.Limitations
The guard sees only project code. It does not check whether the developer account is active, agreements are accepted or package names are registered, and these can delay a first launch by weeks. A `CLEAR.` verdict does not guarantee review approval. The installer edits agent configs (such as `~/.claude/settings.json` and `~/.codex/hooks.json`) and makes backups, but read what it writes first. All tools other than Claude Code need python3. The README gives the licence as OpenRoots ORA 2.3.
How to disable. Run `install.sh --tool <name> uninstall`, for example `install.sh --tool gemini uninstall`. The shared skill stays until at least one tool still uses it.
FAQ
How do I scan a project without installing?
Clone the repository and run `bash app-store-compliance-guard.sh "/path/to/your/app"` from `agent-os/hooks`. Nothing is installed and nothing in the app changes.
What does `NOT CHECKED.` mean?
The guard found no iOS or Android project in the folder or could not write its scan files. Run by hand it exits 1; as a hook it lets the command through.
Which submit commands get blocked?
The hook triggers before upload commands, such as to App Store Connect or Google Play. For Roo Code and Continue the README advises adding `fastlane`, `xcrun altool`, `eas submit` and `gradle bundleRelease` to denied commands.
How do I verify the install worked?
The installer ends with `Install verified.` only after it feeds a submit command to the hook and sees it blocked. A `doctor` mode exists for diagnosis.
Which tools are not wired automatically?
Kiro CLI, Cline, Amp, Goose, Crush, Roo Code, Continue, Aider and Copilot for Xcode. For them the README gives manual steps or advises running the guard by hand before a submit.
Discussion
No questions or reviews yet.
Related
SkillsClaude Code skill that takes an iOS or Flutter app from archive and signing to App Store submission and review rejection recovery.
A Claude Code plugin that audits a mobile app against App Store and Google Play review rules before submission.
A skill that scans an iOS or macOS project for common App Store rejection patterns before you submit
A CLI and Claude Code plugin that find App Store and Google Play rejection causes before you submit, citing the rule for each.
Claude Code skill that audits an iOS app before App Store submission: guideline, code evidence, fix and confidence per finding.
An agent checks Apple app code against every App Store guideline and shows what could trigger a rejection before you submit
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| App Store Compliance Playbook (this card) | no | 429 | |
| App Store Preflight | no | 1,416 | checks an iOS or macOS project for common rejection causes; this one adds Google Play, a blocking hook and an appeal reference |
| App Store Review Guidelines Skill | no | 451 | checks code against every Apple guideline; here the guard stands before the submit command and covers both platforms |
README in short
Guard, skill, command and docs sit in one repository: project scan, preparation checklist and a breakdown of typical mistakes.