skills/swift_context/SKILL.md
Use this skill for semantic codebase analysis and mapping local code dependencies. It provides a semantic engine to query local code context. Use when asking "where is X implemented", "what depends on Y", "find all usages of Z", "what breaks if I change this", or any question about your local project's code structure, dependencies, or impact analysis.
npx skillsauth add swiftzilla/skills swift_contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to map your project's code structure through semantic indexing.
Rebuilds the encrypted semantic index. Run when files have changed significantly.
scripts/swift_context sync --path <PROJECT_ROOT>
Semantic search across the indexed codebase.
scripts/swift_context query "<NATURAL_LANGUAGE_QUERY>"
Analyzes the blast radius of a planned change.
scripts/swift_context impact "<INTENTION_OR_COMPONENT_NAME>"
Run sync in these cases:
.bin file exists in ~/.swiftzilla/cachequery returns irrelevant results~/.swiftzilla/cache — if you switch projects, the old cache may still be used. Always sync with the correct --path after switching projects.query returns semantic matches, not exact text matches. If you need exact string search, use standard grep/find tools instead.impact — stale indexes produce incorrect dependency maps.sync if the index is missing or stalequery to find relevant code locations and understand implementation detailsimpact before making changes to understand what else will be affectedtools
Use this skill when you need expert Swift/iOS architectural guidance, semantic codebase analysis, or PR impact reviews. It provides a senior mentor layer for Swift (SwiftUI, UIKit, Combine, Concurrency) and a semantic engine to query local code context. Trigger this skill to: 1. Validate architectural patterns before implementation using 'ask'. 2. Find and map local code dependencies using 'context'. 3. Analyze the risk and blast radius of a PR using 'review'. 4. Generate system overviews for onboarding using 'onboard'. 5. Troubleshoot runtime crashes with semantic LLDB tools using 'debug'. Activate even if specific keywords are missing but the intent is improving Swift code quality or understanding project structure.
development
Swift Testing framework for unit tests, integration tests, and async testing with modern syntax.
development
SwiftUI framework concepts including property wrappers, state management, and reactive UI patterns.
development
Swift style guidelines covering naming conventions, code organization, and best practices for writing idiomatic Swift code.