A new open-source project called app-store-compliance provides a shell-based pre-submission guard and playbook designed to catch iOS and Android app store rejections before they reach review. Maintained by a single developer, the repository bundles 117 documented rejection patterns mapped to exact Apple and Google guidelines, alongside a registry of 95 tracked regulatory deadlines covering the EU AI Act, DSA, COPPA, and various age verification laws. The tool runs locally, scanning project folders for known compliance failures, and integrates directly into AI coding agents to block submission commands when critical risks are detected.
Local scanning mechanics
The core component is a bash script that takes a path to an Xcode or Android project directory. It parses the project structure and outputs a ranked findings table, classifying issues as critical, high, or medium. Each finding includes the triggering file and line number where applicable, the exact guideline or policy reference, and a concrete fix. The script concludes with a single status line that dictates the next step: BLOCKED if a critical risk is present, CLEAR if the code passes, or NOT CHECKED if the guard cannot locate a valid project structure.
Scan times scale with project size. A small project typically completes in under a second, while larger codebases may take up to a minute. The script prints its runtime at the end of execution. For managed Expo apps lacking native folders, the guard falls back to reading app.json or app.config for purpose strings and privacy manifests, though running npx expo prebuild first ensures native code is covered. The script is designed to be non-destructive; it reads project files, writes scan results to a temporary folder, and leaves the original codebase untouched.
AI agent integration
The repository includes an installer script that configures hooks for 13+ AI coding tools, including Claude Code, Codex, Gemini CLI, Cursor, GitHub Copilot, Grok, Qwen Code, and Windsurf. The installer writes the guard into the tool's native hook directory and registers a skill or plugin that triggers the scan automatically when a submit command is issued. For supported tools, the hook intercepts the upload payload and halts the process if the guard exits non-zero.
The installation process is self-verifying. The script feeds a test submit command to the hook in the tool's native payload format and confirms it blocks successfully. It prints Install verified upon success. If a FAIL line appears, the installer suggests running with the doctor flag to diagnose the issue. The installer preserves existing configuration files, appending new entries without overwriting unrelated settings, and keeps a dated backup of any modified files. It handles tool-specific configuration paths carefully, such as writing to ~/.claude/settings.json for Claude Code, ~/.codex/hooks.json for Codex, or ~/.gemini/settings.json for Gemini CLI. For Gemini CLI versions prior to 0.26, it also enables tools.enableHooks to allow hook execution. Kimi Code receives a marked [[hooks]] block appended to its config file, while Factory Droid writes to ~/.factory/settings.json to avoid conflicts with existing hook directories.
The installer also deploys a shared skill file to ~/.agents/skills/, which every tool except Claude Code reads directly. Claude Code stores its skill in ~/.claude/skills/. The skill contains a structured prompt that instructs the agent to clone the repository, run the installer, verify the hook, execute the guard against the current project, and walk the user through the account readiness checklist. This ensures the agent handles the entire setup sequence without manual command entry.
Illustrative image: blickpixel / Pixabay
For Windows environments, the installer runs through Git Bash and registers hooks for both Bash and PowerShell, widening any legacy Bash-only entries. Developers can preview configuration changes with a --dry-run flag, check the installed version with --version, or remove the entire setup with an uninstall command that strips the hook and skill while preserving other tool configurations.
Coverage and verification limits
The playbook prioritizes the two most common modern rejection causes: missing or mismatched demo accounts with live backends, and privacy declarations that do not match runtime SDK usage. Each pattern in the repository traces back to live Apple or Google policy documents. The project includes a Python script, verify-citations.py, that cross-checks these citations against official sources to ensure the rules are real and not inferred. The tool also provides a pre-submission checklist for account readiness and a metadata audit script for store listings.
The automated guard has clear boundaries. It cannot verify whether a developer account is active, whether program agreements are accepted, or whether Play Console package names are registered—gaps that can delay a first launch for weeks before review even begins. Additionally, automatic hook installation is not universal. Tools like Kiro CLI, Cline, Amp, Goose, and Crush require manual JSON or configuration file edits to trigger the guard. Platforms such as Roo Code, Continue, Aider, and Copilot for Xcode lack pre-command hook support entirely, requiring developers to run the scan manually or configure git pre-push hooks before submission.
The regulatory deadline tracker monitors 95 specific dates across the EU AI Act, DSA, COPPA, and regional age laws, flagging upcoming compliance windows within a 90-day shipping radius. For non-developers, the repository provides a plain English checklist that isolates the first two critical verification steps, allowing product managers and QA teams to validate account and program readiness without touching the codebase. Developers can wire the guard into their build pipeline, while non-developers simply follow the checklist to navigate submission safely.
The repository is free and open source. Developers can clone the project, run the installer for their specific environment, and update the guard by pulling the latest changes and re-running the setup command. The project explicitly requests no payment or enterprise licensing, relying instead on community stars and forks to sustain maintenance.
Sources
PNEUMETRON EDITORIAL
Pneumetron's pipeline pairs AI-assisted drafting with human editorial review before publishing — our goal is to make staying informed easier, not to replace real reporting.




