app-completeness-check

Scan iOS/macOS source and config files for placeholder content and non-production endpoints.

13|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/cruisediary/apple-app-review-skills --skill app-completeness-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-completeness-check
Source: https://github.com/cruisediary/apple-app-review-skills/tree/main/skills/quality/app-completeness-check
Command: npx skills add https://github.com/cruisediary/apple-app-review-skills --skill app-completeness-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects placeholder content, stub UI, hardcoded test credentials, and non-production endpoints that signal an incomplete app to reviewers under Guideline 2.1.

Core Features & Use Cases

  • Identify placeholder copy such as "Lorem ipsum" in production code and UI to avoid rejection.
  • Flag visible Coming Soon or Not Yet Available UI elements that signal unfinished features.
  • Validate metadata URLs and network endpoints are production-ready and accessible at review time.
  • Provide a prioritized findings list with file paths and line numbers to guide fixes.

Quick Start

Invoke the app-completeness-check skill against an iOS/macOS project to detect placeholders, non-production URLs, and incomplete UI before App Store submission.

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?

Checking iOS apps for placeholder content involves scanning Swift, Objective-C, and configuration files to detect stub UI, hardcoded test credentials, and non-production endpoints that violate Guideline 2.1 completeness standards.

Why does my app get rejected under Guideline 2.1 for unfinished features?

App rejections under Guideline 2.1 happen when reviewers find unfinished features like placeholder copy such as Lorem ipsum, Coming Soon UI elements, or inaccessible metadata URLs that signal the app is incomplete and not production-ready.

How do I find hardcoded test credentials in Swift and Objective-C source code?

To find hardcoded test credentials in Swift and Objective-C source code, scan production code and configuration files to identify non-production endpoints and validate that network URLs are accessible at review time.

Can I scan configuration files for non-production endpoints before submission?

Yes, scanning configuration files for non-production endpoints validates metadata URLs and network configurations across source code to ensure they are production-ready and accessible before App Store submission.

What is the best way to detect stub UI elements in an iOS project?

Detecting stub UI elements in an iOS project involves scanning source files for visible Coming Soon or Not Yet Available markers, producing a prioritized findings report with exact file paths and line numbers.

What limitations exist when scanning macOS apps for App Store completeness issues?

Scanning macOS apps for App Store completeness issues is limited to validating Swift, Objective-C, and Config sources, meaning completeness problems in other code formats may not surface in the findings report.