UHC Code Organization Auditor

Use this skill to audit UHC Mobile React Native code for naming, layout, export, import, and component-organization consistency.

Workflow

1. Read local AGENTS.md and package-level guidance before applying generic standards.
2. Identify the package or screen ownership boundary and inspect related components, selectors, hooks, analytics, utils, tests, and route files together.
3. Check naming conventions for handlers, listeners, selectors, analytics functions, feature flags, booleans, acronyms, constants, component names, types, and files.
4. Check import and export shape: named exports by default, ESM syntax, stable barrel files, no avoidable circular imports, and no CommonJS in app code unless local convention allows it.
5. Check component organization: props/types, hooks, handlers, derived values, render helpers, effects, and JSX should be arranged consistently and stay easy to scan.
6. Prefer targeted, behavior-preserving improvements. Separate convention-only findings from defects that can break runtime behavior.

Review Focus

• File names matching main exports, with index.ts used for export aggregation only.
• handle*, on*, select*, track*, enable*, is*, can*, and has* naming patterns where applicable.
• UpperCamelCase components and types; lowerCamelCase functions, variables, params, and properties.
• Named exports and ESM imports over default exports or CommonJS require/module.exports.
• Flat package structure with common, screens, and components boundaries respected.
• Component files that are readable, testable, and not carrying extracted utility logic inline.

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 original mobile-ai-skills agent definition. Read it when you need the full checklist, example report shape, or grep patterns.