/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
$ 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
/apollo-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
apollo-status.mdApollo 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 Apollo removal migration progress.
Steps
1. Read the Tracking File
Read `docs/apollo-migration-status.md` and parse the migration table.
2. Calculate Summary Statistics
Count repositories by status:
- **Done:** Fully migrated to GraphQLClientProtocol
- **Deleted:** Removed (no longer needed)
- **In-Progress:** Currently being worked on
- **Todo:** Not yet started
- **Not-Needed:** Already uses non-Apollo pattern or not a repository
3. Show Progress
Display:
## Apollo Migration Progress
| Status | Count | Percentage |
|-------------|-------|------------|
| Done | X | X% |
| Deleted | X | X% |
| In-Progress | X | X% |
| Todo | X | X% |
| Not-Needed | X | X% |
| **Total** | **X** | **100%** |
Progress bar: [=========>..........] X%
4. Show In-Progress Repos
If any repos are in-progress, list them with their owner:
### Currently In-Progress
| Repository | Owner | Tier |
|------------|-------|------|
| ... | ... | ... |
5. Recommend Next Repos
Suggest the next 5 repositories to tackle, prioritizing: 1. **Tier 1** (simplest) first 2. Fewer consumers = easier migration 3. Repos in `<scheme>/Repositories/` before `<scheme>/Modules/` (more standardized)
### Recommended Next
| Repository | Tier | Consumers | Location |
|------------|------|-----------|----------|
| ... | ... | ... | ... |
6. Show Recently Completed
List the last 5 completed migrations with their PR links (if available).
Read more
Apollo 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 Apollo removal migration progress.
Steps
1. Read the Tracking File
Read `docs/apollo-migration-status.md` and parse the migration table.
2. Calculate Summary Statistics
Count repositories by status:
- **Done:** Fully migrated to GraphQLClientProtocol
- **Deleted:** Removed (no longer needed)
- **In-Progress:** Currently being worked on
- **Todo:** Not yet started
- **Not-Needed:** Already uses non-Apollo pattern or not a repository
3. Show Progress
Display:
## Apollo Migration Progress | Status | Count | Percentage | |-------------|-------|------------| | Done | X | X% | | Deleted | X | X% | | In-Progress | X | X% | | Todo | X | X% | | Not-Needed | X | X% | | **Total** | **X** | **100%** | Progress bar: [=========>..........] X%
4. Show In-Progress Repos
If any repos are in-progress, list them with their owner:
### Currently In-Progress | Repository | Owner | Tier | |------------|-------|------| | ... | ... | ... |
5. Recommend Next Repos
Suggest the next 5 repositories to tackle, prioritizing: 1. **Tier 1** (simplest) first 2. Fewer consumers = easier migration 3. Repos in `<scheme>/Repositories/` before `<scheme>/Modules/` (more standardized)
### Recommended Next | Repository | Tier | Consumers | Location | |------------|------|-----------|----------| | ... | ... | ... | ... |
6. Show Recently Completed
List the last 5 completed migrations with their PR links (if available).
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-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 - /code-review
Review code quality applying DRY, SOLID, naming, and formatting standards
Open command

