ios-clean

Removes DebugBridge SPM package and associated #if DEBUG code from iOS apps before production builds.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill ios-clean-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-clean
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.claude/skills/gstack/ios-clean
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill ios-clean-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes leftover debug instrumentation from iOS apps that were tested using gstack's /ios-qa skill, including the DebugBridge SPM package, all #if DEBUG code, StateServer, DebugOverlay, and accessor codegen output. This cleanup is essential to reduce app bundle size, prevent debug features from being exposed to end users, and ensure compliance with App Store production application guidelines.

Core Features & Use Cases

  • Complete Debug Code Removal: Automatically strips the DebugBridge SPM package and all associated debug-only code, hooks, and generated accessor code from your iOS project.
  • Pre-Release Preparation: Use this Skill after completing debug testing with gstack tools to clean all debug instrumentation before building your production release version for App Store submission.
  • Safety-First Design: Uses the structural Release-build guard (Package.swift conditional + CI swift build -c release check) as the safety-critical path to avoid accidentally removing production code.

Quick Start

Use the ios-clean skill to remove all DebugBridge debug instrumentation and #if DEBUG wiring from your iOS app to prepare it for a production release build.

Frequently Asked Questions about ios-clean

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

FAQPage Schema
How do I remove debug code from an iOS app before an App Store release build?

To remove debug code from an iOS app before an App Store release build, you need to strip out debug-only dependencies, #if DEBUG wiring, and debug overlays to reduce bundle size and ensure production compliance. This cleanup prevents internal debug features from being exposed to end users.

What is the best way to clean up SPM package dependencies for iOS production release?

Cleaning up SPM package dependencies for iOS production release requires removing debug-instrumentation packages, associated StateServer hooks, and generated accessor code from your Xcode project. This ensures your app bundle remains lightweight and complies with App Store production application guidelines.

Does my iOS app need debug instrumentation removed if I used a debug testing skill?

Yes, if you used debug testing instrumentation in your iOS app, it must be removed prior to production release. Leftover debug bridges and #if DEBUG code bloat app bundle size and expose internal debug features to end users, violating App Store production guidelines.

How do I eliminate #if DEBUG wiring and DebugOverlay from my Xcode project?

To eliminate #if DEBUG wiring and DebugOverlay from your Xcode project, you must remove the associated SPM package, StateServer, and accessor codegen output. This strips all debug-only hooks and generated code, preparing your iOS application for a clean production build.

Can I safely strip debug-only code without accidentally removing production code?

You can safely strip debug-only code by using a structural Release-build guard as the safety-critical path. Relying on Package.swift conditional checks and CI swift build release verification prevents accidentally removing production code during the debug instrumentation cleanup process.