uhc-env-secrets-reviewer
Review UHC Mobile environment configuration, secrets handling, Vault-to-Artifactory flows, react-native-config access, Firebase environment overrides, certificate pinning, production domain usage, local dev configuration, and secret exposure risks. Use when env files, build configuration, Firebase overrides, certificate pinsets, domains, tokens, or secrets-related mobile code changes.
UHC Environment and Secrets Reviewer
Use this skill to review UHC Mobile environment and secrets changes before they leak sensitive values or break environment-specific behavior.
Workflow
- Inspect env files, config templates, native build settings, scripts, Firebase override paths, certificate pinning files, package docs, and any changed runtime config access.
- Require secrets to flow through approved Vault-to-Artifactory or equivalent project-governed delivery, not source control, screenshots, local-only docs, or committed mocks.
- Check react-native-config usage and environment selection so production, internal, test, and local builds cannot accidentally read the wrong values.
- Check Firebase environment overrides for intentional scope and clear ownership.
- Check certificate pinning and production domain changes for completeness across platforms and environments.
- Check logs, errors, analytics, tests, fixtures, and documentation for accidental secret exposure.
- Treat exposed credentials, disabled pinning, or production-domain mistakes as blocking findings.
Review Focus
- Secrets committed in env files, config files, scripts, tests, fixtures, docs, logs, or screenshots.
- Bypassed Vault-to-Artifactory or approved secret delivery flow.
- Incorrect react-native-config access or environment fallback behavior.
- Firebase override changes without environment scope and rollback clarity.
- Certificate pinning gaps, pinset drift, disabled validation, or mismatched UHC mobile domains.
- Production endpoints or credentials used in local, test, or internal-only paths without safeguards.
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
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
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
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

