How do I install the Swift Context skill?

Run npx skillmds@latest add swiftzilla/swift-context 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 Context 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 Context?

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 Context free to use?

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

Who published Swift Context?

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

Swift Context by swiftzilla — Agent Skill

Name: Swift Context
Author: swiftzilla

Swift Context

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.

swiftzilla 2bf2b85 3 files · 27.8 MB Updated Sep 17, 2026

File contents

Swift Context: Local Semantic Intelligence

Use this skill to map your project's code structure through semantic indexing.

Commands

sync

Rebuilds the encrypted semantic index. Run when files have changed significantly.

scripts/swift_context sync --path <PROJECT_ROOT>

query

Semantic search across the indexed codebase.

scripts/swift_context query "<NATURAL_LANGUAGE_QUERY>"

impact

Analyzes the blast radius of a planned change.

scripts/swift_context impact "<INTENTION_OR_COMPONENT_NAME>"

When to Sync

Run sync in these cases:

Missing cache: No corresponding .bin file exists in ~/.swiftzilla/cache
Stale index: Project files are newer than the cached index
Unexpected results: After a refactor, query returns irrelevant results

Gotchas

The index is encrypted and cached in ~/.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.
After major refactors, always re-sync before running impact — stale indexes produce incorrect dependency maps.

Workflow

Sync: Run sync if the index is missing or stale
Query: Use query to find relevant code locations and understand implementation details
Impact: Use impact before making changes to understand what else will be affected

---name: swift-contextdescription: 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.license: Proprietary---# Swift Context: Local Semantic IntelligenceUse this skill to map your project's code structure through semantic indexing.## Commands### syncRebuilds the encrypted semantic index. Run when files have changed significantly.```bashscripts/swift_context sync --path <PROJECT_ROOT>```### querySemantic search across the indexed codebase.```bashscripts/swift_context query "<NATURAL_LANGUAGE_QUERY>"```### impactAnalyzes the blast radius of a planned change.```bashscripts/swift_context impact "<INTENTION_OR_COMPONENT_NAME>"```## When to SyncRun `sync` in these cases:1. **Missing cache**: No corresponding `.bin` file exists in `~/.swiftzilla/cache`2. **Stale index**: Project files are newer than the cached index3. **Unexpected results**: After a refactor, `query` returns irrelevant results## Gotchas- The index is encrypted and cached in `~/.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.- After major refactors, always re-sync before running `impact` — stale indexes produce incorrect dependency maps.## Workflow1. **Sync**: Run `sync` if the index is missing or stale2. **Query**: Use `query` to find relevant code locations and understand implementation details3. **Impact**: Use `impact` before making changes to understand what else will be affected

Frequently asked questions