← ClaudeAtlas

swift-auditlisted

Audits planning docs, story files, and Swift source code against the Swift/SwiftUI guidance in docs/setup/swift/, producing a remediation story file with one AC per finding. Use when the user asks whether Swift or SwiftUI code follows current patterns, before a release, after a guidance refresh, or says "swift audit", "audit swift", "audit codebase", or "check swift patterns".
rterakedis/leanwheel-skills · ★ 2 · AI & Automation · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Swift Audit Skill **Goal:** Scan the entire project — planning docs, story files, and Swift source code — against the guidance in `docs/setup/swift/`. Collate all findings into a single remediation story file that `/dev-story` can implement directly. **Requires:** `docs/setup/swift/` must exist. If absent, tell the user to run `/setup` (for a new project) or `/refresh-swift` (to populate an existing project's swift docs). --- ## Step 1 — Load Guidance Read all files present in `docs/setup/swift/`: ```bash ls docs/setup/swift/ ``` Read each file completely. These are the standards everything will be measured against. Pay particular attention to `anti-patterns.md` — it contains the hard rejection list used for code scanning. --- ## Step 2 — Inventory the Project Run these commands to understand what exists: ```bash # Planning docs ls docs/prd.md docs/architecture.md docs/epics.md 2>/dev/null # Story files find docs/epics -name "*.md" | sort # Swift source files (exclude build artifacts and dependencies) find . -name "*.swift" \ ! -path "*/DerivedData/*" \ ! -path "*/.build/*" \ ! -path "*/Pods/*" \ ! -path "*/Packages/*" \ | sort # Existing audit files (to avoid re-auditing completed work) find docs/epics -name "swift-audit-*.md" | sort ``` Note what is present. If no Swift source files exist yet, skip Step 4 and note "no source to audit" in the report. --- ## Step 3 — Audit Planning Docs Read each planning doc that exists and reason against the gu