app-completeness-check

Name: app-completeness-check
Availability: InStock
Author: wilderness

Detects placeholder content, hardcoded credentials, and non-production endpoints in iOS projects before App Store submission.

Updated Aug 14, 2026

Search Tags:#swift #ios #app store review #placeholder detection #rejection prevention #guideline 2.1 #app completeness

Ready to run

npx skills add https://github.com/tvh25082004/Badminton --skill app-completeness-check-tvh25082004

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: app-completeness-check
Source: https://github.com/tvh25082004/Badminton/tree/main/.claude/skills/apple-app-review/quality/app-completeness-check
Command: npx skills add https://github.com/tvh25082004/Badminton --skill app-completeness-check-tvh25082004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Apps submitted to the App Store with leftover placeholder text, "Coming Soon" tabs, hardcoded test credentials, or staging endpoints are routinely rejected under Apple Guideline 2.1 (App Completeness). This Skill scans an iOS/macOS codebase before submission to catch these rejection signals early. ## Core Features & Use Cases - Placeholder Content Detection: Greps Swift, strings, and plist files for Lorem ipsum, TODO/FIXME, and "Coming Soon" UI copy that reviewers treat as incomplete-app signals. - Security & Environment Checks: Finds hardcoded test credentials (e.g., [email protected], password123) and non-production endpoints (localhost, staging, .dev domains) in network configuration. - Minimum Functionality Audit: Flags WebView-only apps that violate Guideline 4.2 by wrapping a website without native functionality. - Use Case: Before submitting a build, run the check on your project root to get a prioritized findings list (CRITICAL/HIGH/MEDIUM) with file paths, line numbers, and remediation TODOs mapped to specific Apple guidelines. ## Quick Start Run the app completeness check on my iOS project and list any placeholder content, hardcoded credentials, or staging endpoints that could cause an App Store rejection.

Frequently Asked Questions about app-completeness-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check my iOS app for placeholder content before App Store submission?▼

Grep your Swift and .strings files for patterns like "Lorem ipsum", "Coming Soon", "TODO", and "FIXME". Any placeholder text found in UI contexts is a rejection signal under Guideline 2.1 and must be replaced with real content before submission.

What causes App Store rejection under Guideline 2.1?▼

Common causes include Lorem ipsum placeholder text, visible "Coming Soon" tabs, hardcoded test credentials, staging or localhost endpoints, broken support URLs, and mandatory account creation with no demo mode for reviewers.

Does this check work with React Native or Flutter projects?▼

Yes. While the grep patterns target Swift and Objective-C source files, the Skill's constraints state it works on Swift, Objective-C, React Native, and Flutter projects for pre-submission completeness review.

Why is a WebView-only app rejected by Apple?▼

Guideline 4.2 requires apps to be useful, unique, and app-like. A thin wrapper that only displays a website in a WKWebView provides no native value and is rejected as a glorified website; the app must offer functionality beyond a browser experience.

Can the check modify my source files to fix issues automatically?▼

No. The Skill is strictly read-only and makes no file edits or network calls. It outputs a prioritized findings list with TODO items, file paths, and line numbers so developers can apply fixes themselves.