/swift6-status
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase
$ npx -y skills add carloshpdoc/ios-workflow-claude --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/swift6-status
Context preview
What this command does when you run it.
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase
Command definition
swift6-status.mdSwift 6 Migration Status
> **Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase search for flag/font files), or ask if they cannot be inferred. This plugin ships no per-project config.
Show the current Swift 6 migration progress across all blocker categories.
Steps
1. Read the Tracking File
Read `docs/swift6-migration-status.md` and parse the progress table and config checklist.
2. Live Scan (Optional Verification)
Run a quick grep to verify counts against the actual codebase:
# Current @MainActor coverage on ViewModels
grep -r "@MainActor" <scheme>/Modules --include="*ViewModel*.swift" -l | wc -l
# Remaining DispatchQueue.main.async calls
grep -r "DispatchQueue.main.async" <scheme>/ --include="*.swift" -l | wc -l
# Remaining completion handlers
grep -r "completion:" <scheme>/ --include="*.swift" -l | wc -l
# Singletons
grep -r "static let shared\|static var shared" <scheme>/ --include="*.swift" | wc -l
Compare live counts against the tracking file. Flag discrepancies if any.
3. Show Config Status
Display the config checklist items with their current status (done/pending).
4. Show Progress Table
Display the progress table with a visual progress bar:
## Swift 6 Migration Progress
| Category | Total | Done | Remaining | Status |
|----------|-------|------|-----------|--------|
| ... | ... | ... | ... | ... |
Overall Progress: [=========>..........] X%
5. Show Recent Activity
List the last 5 entries from the Execution Log:
### Recent Activity
| Date | Category | Files Changed | Dev | PR |
|------|----------|---------------|-----|----|
| ... | ... | ... | ... | ...|
6. Recommend Next Fix
Based on the analysis priority order, recommend the next `/swift6-fix` to run:
Priority order: 1. Config changes (if not done) 2. `@MainActor` on ViewModels (highest impact, enables other fixes) 3. Mutable singletons (small count, high risk) 4. `DispatchQueue.main.async` (mechanical, large count) 5. Completion handlers (mechanical, largest count) 6. `@Sendable` annotations (can be done last) 7. Delegate patterns (often resolved by @MainActor)
### Recommended Next
Run: `/swift6-fix <type>` — <reason>
Estimated files: <count>
7. Show Known Blockers
Display the external dependency blockers table from the status file.
Notes
- Status file: `docs/swift6-migration-status.md`
- Analysis doc: [Notion — Swift 6 Migration](<notion-swift6-tracker-url>)
- Always verify live counts against tracked counts
- When counts diverge significantly, update the status file
Read more
Swift 6 Migration Status
> **Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase search for flag/font files), or ask if they cannot be inferred. This plugin ships no per-project config.
Show the current Swift 6 migration progress across all blocker categories.
Steps
1. Read the Tracking File
Read `docs/swift6-migration-status.md` and parse the progress table and config checklist.
2. Live Scan (Optional Verification)
Run a quick grep to verify counts against the actual codebase:
# Current @MainActor coverage on ViewModels grep -r "@MainActor" <scheme>/Modules --include="*ViewModel*.swift" -l | wc -l # Remaining DispatchQueue.main.async calls grep -r "DispatchQueue.main.async" <scheme>/ --include="*.swift" -l | wc -l # Remaining completion handlers grep -r "completion:" <scheme>/ --include="*.swift" -l | wc -l # Singletons grep -r "static let shared\|static var shared" <scheme>/ --include="*.swift" | wc -l
Compare live counts against the tracking file. Flag discrepancies if any.
3. Show Config Status
Display the config checklist items with their current status (done/pending).
4. Show Progress Table
Display the progress table with a visual progress bar:
## Swift 6 Migration Progress | Category | Total | Done | Remaining | Status | |----------|-------|------|-----------|--------| | ... | ... | ... | ... | ... | Overall Progress: [=========>..........] X%
5. Show Recent Activity
List the last 5 entries from the Execution Log:
### Recent Activity | Date | Category | Files Changed | Dev | PR | |------|----------|---------------|-----|----| | ... | ... | ... | ... | ...|
6. Recommend Next Fix
Based on the analysis priority order, recommend the next `/swift6-fix` to run:
Priority order: 1. Config changes (if not done) 2. `@MainActor` on ViewModels (highest impact, enables other fixes) 3. Mutable singletons (small count, high risk) 4. `DispatchQueue.main.async` (mechanical, large count) 5. Completion handlers (mechanical, largest count) 6. `@Sendable` annotations (can be done last) 7. Delegate patterns (often resolved by @MainActor)
### Recommended Next Run: `/swift6-fix <type>` — <reason> Estimated files: <count>
7. Show Known Blockers
Display the external dependency blockers table from the status file.
Notes
- Status file: `docs/swift6-migration-status.md`
- Analysis doc: [Notion — Swift 6 Migration](<notion-swift6-tracker-url>)
- Always verify live counts against tracked counts
- When counts diverge significantly, update the status file
Reusable Claude Code slash-commands, skills, and workflows extracted from real iOS / backend projects. Packaged as three installable plugins - register the marketplace and /plugin install what you need.
Repo: carloshpdoc/ios-workflow-claude
Other commands on ios-workflow-claude.
- /apollo-check
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase
Open command - /apollo-migrate
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase
Open command - /apollo-review
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase
Open command - /apollo-status
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase
Open command - /apollo-tasks
**Project context:** Values in angle brackets below (e.g. `<scheme>`, `<JIRA_KEY>`, `<flag-key-enum>`) are resolved at runtime — detect them from the project (`xcodebuild -list -json` for the scheme, `git`/`gh` for repo & owner, the branch name for the Jira key, a codebase
Open command - /bump
Bump the app version or build number across all targets in the current project.
Open command

