How do I install the Swift Deep Insight skill?

Run npx skillmds@latest add swiftzilla/swift-deep-insight in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Swift Deep Insight safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Swift Deep Insight?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Swift Deep Insight free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Proprietary.

Who published Swift Deep Insight?

swiftzilla (@swiftzilla) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Swift Deep Insight by swiftzilla — Agent Skill

Name: Swift Deep Insight
Author: swiftzilla

Swift Deep Insight

Identify unused code in Swift projects using the Swift compiler's index store. Detects unused classes, structs, functions, properties, protocols, and more. Use when cleaning up dead code, auditing codebase health, preparing for refactoring, or reviewing PR scope — even if they don't mention "index store" or "dead code" but describe removing unused or unreachable code.

swiftzilla 5c7277c 3 files · 27.7 MB Updated Sep 17, 2026

File contents

Swift Deep Insight: Unused Code Detection

Detect unused (dead) code in Swift projects using the Swift compiler's index store.

Prerequisites

Xcode Projects

Build the project in Xcode first — the index store is created automatically at ~/Library/Developer/Xcode/DerivedData/<Project>/Index/DataStore.

SPM Projects

Build with xcodebuild -scheme <scheme> build or swift build.

Commands

Run from the project root or specify a path:

# Scan current directory
swift run swift-deep-insight --project-path .

# Verbose output
swift run swift-deep-insight --project-path . --verbose

# Xcode-clickable output (file:line:column:)
swift run swift-deep-insight --project-path . --xcode-format

# Include public declarations (normally excluded)
swift run swift-deep-insight --project-path . --include-public

Options

Option	Description
`--project-path`	Path to Swift project (default: current directory)
`--verbose`	Enable detailed logging
`--xcode-format`	Output in Xcode-compatible format (file:line:column:)
`--include-public`	Include public declarations in unused analysis
`--exclude-tests`	Exclude test targets from analysis
`--build`	Build the project before scanning (default: false)

Gotchas

No index store = limited results: Without the index store, analysis falls back to source-only parsing and misses cross-file references. Always build first.
Runtime reflection is invisible: Code used via responds(to:), perform(), or other runtime mechanisms will appear unused even though it's called.
External packages are not analyzed: Only your project's code is scanned, not dependencies.
Public declarations are excluded by default: Public/API symbols are assumed to be used by consumers. Use --include-public to override.
Entry points are auto-detected: main, @main, @NSApplicationMain, and AppDelegate are treated as roots — everything reachable from them is "used".

Workflow

Build: Ensure the project is built so the index store is fresh
Scan: Run the analyzer with appropriate flags
Review: Examine unused declarations — verify each is truly dead code before removing
Validate: After removal, rebuild and run tests to confirm nothing was incorrectly classified

---name: swift-deep-insightdescription: Identify unused code in Swift projects using the Swift compiler's index store. Detects unused classes, structs, functions, properties, protocols, and more. Use when cleaning up dead code, auditing codebase health, preparing for refactoring, or reviewing PR scope — even if they don't mention "index store" or "dead code" but describe removing unused or unreachable code.license: Proprietary---# Swift Deep Insight: Unused Code DetectionDetect unused (dead) code in Swift projects using the Swift compiler's index store.## Prerequisites### Xcode ProjectsBuild the project in Xcode first — the index store is created automatically at `~/Library/Developer/Xcode/DerivedData/<Project>/Index/DataStore`.### SPM ProjectsBuild with `xcodebuild -scheme <scheme> build` or `swift build`.## CommandsRun from the project root or specify a path:```bash# Scan current directoryswift run swift-deep-insight --project-path .# Verbose outputswift run swift-deep-insight --project-path . --verbose# Xcode-clickable output (file:line:column:)swift run swift-deep-insight --project-path . --xcode-format# Include public declarations (normally excluded)swift run swift-deep-insight --project-path . --include-public```### Options| Option | Description ||--------|-------------|| `--project-path` | Path to Swift project (default: current directory) || `--verbose` | Enable detailed logging || `--xcode-format` | Output in Xcode-compatible format (file:line:column:) || `--include-public` | Include public declarations in unused analysis || `--exclude-tests` | Exclude test targets from analysis || `--build` | Build the project before scanning (default: false) |## Gotchas- **No index store = limited results**: Without the index store, analysis falls back to source-only parsing and misses cross-file references. Always build first.- **Runtime reflection is invisible**: Code used via `responds(to:)`, `perform()`, or other runtime mechanisms will appear unused even though it's called.- **External packages are not analyzed**: Only your project's code is scanned, not dependencies.- **Public declarations are excluded by default**: Public/API symbols are assumed to be used by consumers. Use `--include-public` to override.- **Entry points are auto-detected**: `main`, `@main`, `@NSApplicationMain`, and `AppDelegate` are treated as roots — everything reachable from them is "used".## Workflow1. **Build**: Ensure the project is built so the index store is fresh2. **Scan**: Run the analyzer with appropriate flags3. **Review**: Examine unused declarations — verify each is truly dead code before removing4. **Validate**: After removal, rebuild and run tests to confirm nothing was incorrectly classified

Frequently asked questions