Git
v1.0.0

appstore-rejection

by @devsemih0 pulls
URLopenbooklet.com/s/appstore-rejection
Pinnedopenbooklet.com/s/[email protected]
APIGET /api/v1/skills/appstore-rejection

Diagnoses an App Store rejection and drafts the Resolution Center reply. Parses an App Review rejection message (pasted text, a file, or a screenshot), maps every cited guideline (e.g. 'Guideline 2.1 - Performance - App Completeness', '5.1.1(v)', '4.8') and ITMS email error (e.g. ITMS-91053 missing API declaration) to the exact rule, finds the root cause in the project code with file:line evidence, proposes fixes, and writes a reply or App Review Board appeal. Works with native Swift/Obj-C, Flutter, React Native, Expo, KMP, .NET MAUI, Capacitor/Cordova/Ionic, and Unity. Use when the user says 'app rejected', 'rejection', 'Resolution Center', 'Guideline 4.3', 'app review rejected my app', 'Apple rejected', 'ITMS-91053', 'binary rejected', or pastes an App Review message.

Auto-indexed from devsemih/appstore-review-skill

Are you the author? Claim this skill to take ownership and manage it.

Related Skills

@openbooklet

graceful-error-recovery

Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.

1.1K0
@openbooklet

audience-aware-communication

Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.

1.1K0
@openbooklet

Refactoring Expert

Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.

600
@openbooklet

Research Expert

Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.

600
@openbooklet

clarify-ambiguous-requests

Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.

1.1K0
@openbooklet

structured-step-by-step-reasoning

Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.

1.1K0