When To Use
- Reviewing or authoring a React Native component and suspecting unnecessary layout wrappers
- Reducing native view depth to improve rendering performance
- Flagging non-interactive containers that are missing
accessible={false}to lower accessibility node count - Running a broad audit across a folder or the entire project
Workflow
See the repo overlay for the full step-by-step playbook (locate files → identify patterns A–F → format findings → ask before fixing → verify tests → open PR → risk report). At a high level:
- Locate the target file(s) based on user input (path, component name, folder,
--all, or git diff) - Identify removable wrappers (Patterns A–E) and accessibility gaps (Pattern F)
- Report findings grouped by file with a summary table
- Ask the user whether to fix all, fix one by one, or just report
- If fixing: apply edits, run tests per file, then open a PR if requested