logging-setup_skill

Overview

This skill generates a structured logging infrastructure using Apple's os.log/Logger to replace print() statements. It helps teams add categorized, privacy-aware, and performant logging across Swift apps (iOS, macOS) and provides migration guidance from print().

How this skill works

The skill inspects the codebase for print() calls and any existing os.log/Logger usage, then offers audit results or generates a new AppLogger.swift with subsystem and categories. It can run in audit, generate, or migrate modes to report print locations, create a logging facade, or automatically convert print() calls to Logger invocations with privacy annotations.

When to use it

• When you want to replace print() statements with structured logging
• When adding app-wide logging with subsystem/category separation
• When you need privacy-safe logging (.public/.private/.sensitive)
• When preparing debug vs Release logging behavior
• When auditing a codebase for ad-hoc print debugging

Best practices

• Use categories (Network, Auth, UI, Data, etc.) to filter logs in Console.app
• Annotate sensitive values with .private or .sensitive to avoid leaking data
• Prefer deferred Logger interpolation for performance in Release builds
• Keep a single AppLogger facade to centralize subsystem and category definitions
• Run an audit pass to classify print() uses before bulk migration

Example use cases

• Audit: produce a file-by-file report of print() occurrences and suggested severity
• Generate: create Logging/AppLogger.swift with default categories and usage examples
• Migrate: replace print("User: (email)") with AppLogger.auth.info("User: (email, privacy: .private)")
• Setup: add a logging bridge during rollout to avoid breaking runtime behavior
• Debugging: add temporary debug logs that compile out in Release builds