uhc-federation-integration-reviewer
Review UHC Mobile federated module integrations for approved V2 package usage, host-app data access, event sending, analytics, navigation, API client usage, accessibility support, session behavior, route mapping, and deprecated V1 package usage. Use when working on UHC Mobile federation packages or integrating a federated module with the host app.
UHC Federation Integration Reviewer
Use this skill to review whether a UHC Mobile federated module integrates with the host app through approved V2 contracts.
Workflow
- Inspect the federated package boundary, package.json, imports, host integration points, route configuration, API clients, analytics, and accessibility usage.
- Require V2 package imports from @uhg-uhc-mobile/federation for host data and host events, @uhg-uhc-mobile/uhc-mobile-api for backend calls, and @uhg-uhc-mobile/accessibility for accessibility helpers when applicable.
- Flag deprecated @optum-mobile-fmd/* package usage and direct host-app internal coupling.
- Check data access patterns: use hooks in components and getters/utilities in non-component code according to local package conventions.
- Check outgoing events: navigation, analytics, SSO, and other host events should use the federation contract rather than bespoke event emitters.
- Check session behavior, route mapping, error handling, and token handling at the boundary.
- Report blocking integration issues before style or cleanup findings.
Review Focus
- Deprecated @optum-mobile-fmd/user, config, event-hub, analytics, or navigation imports.
- Direct imports from host internals instead of the federation contract.
- API calls that bypass the approved @uhg-uhc-mobile/uhc-mobile-api client or token injection pattern.
- Missing or inconsistent route mapping, session handling, host navigation events, or analytics events.
- Accessibility gaps in federated UI where the approved package should be used.
Output
- Lead with findings ordered by severity, with file and line references when possible.
- Separate blocking issues from high, medium, and low priority recommendations.
- Explain impact in mobile-user terms: security exposure, broken rollout, jank, inaccessible flow, analytics drift, build/runtime failure, or maintainability risk.
- Include specific remediation guidance. Keep code snippets small unless the user asks for an implementation.
- If no issues are found, say so clearly and note any meaningful test or verification gaps.
References
references/review-guide.md: Migrated detailed review guide from the originalmobile-ai-skillsagent definition. Read it when you need the full checklist, example report shape, or grep patterns.
Related Assets
dependency-management-reviewer
Review React Native and UHC Mobile dependency additions for maintenance status, React Native compatibility, New Architecture readiness, security vulnerabilities, bundle impact, license and ownership risk, justification, alternatives, and approved federation package usage. Use when package.json, lockfiles, native modules, or third-party package choices change.
Owner: optum-tech-compute
file-structure-auditor
Review React Native and UHC Mobile code for file structure, file naming, related-file grouping, folder organization, modal placement, utility extraction, and package boundary standards. Use when asked to audit directories, organize components, review screen/package layout, or clean up UHC Mobile file structure.
Owner: optum-tech-compute
react-native-performance-review
Review React Native code for performance issues including unnecessary re-renders, inline functions, missing memoization, inefficient lists, context overuse, missing cleanup, and other mobile-specific performance problems. Use when asked to check performance, optimize React Native code, reduce jank, or review performance-critical mobile changes.
Owner: optum-tech-compute
react-native-security-review
Review React Native code for security vulnerabilities including PII/PHI storage, authorization bypass risks, secrets handling, token exposure, unvalidated identifiers, unsafe logging, mobile storage risks, and other security-critical mobile issues. Use when asked to check security, sensitive data handling, authentication, authorization, storage, logging, or network-related React Native changes.
Owner: optum-tech-compute
uhc-analytics-reviewer
Review UHC Mobile analytics implementations for .analytics.ts isolation, track-prefixed functions, Adobe payload casing, analytics constants, screenNameMapEntries updates, route mapping, A/B test tracking, event placement, and federated analytics events. Use when adding or changing mobile analytics, tracking hooks, navigation tracking, or Adobe payloads.
Owner: optum-tech-compute
uhc-code-organization-auditor
Audit UHC Mobile code organization, naming conventions, file structure, import/export patterns, component section ordering, selector and analytics naming, feature-flag naming, and module boundaries before feature merges or cleanup work. Use when reviewing UHC Mobile React Native packages for maintainability and repository convention drift.
Owner: optum-tech-compute

