page-review

Review React Native page and feature directories for architectural convention drift.

Updated Jun 14, 2024
One-click install
npx skills add https://github.com/Yimura/RemoteUnlockApp --skill page-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: page-review
Source: https://github.com/Yimura/RemoteUnlockApp/tree/main/.claude/skills/page-review
Command: npx skills add https://github.com/Yimura/RemoteUnlockApp --skill page-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review a page or feature in the RemoteUnlockApp React Native codebase for structural drift, convention mismatches, and architectural smells without mixing review work with implementation changes.

Core Features & Use Cases

  • Folder and barrel checks: Verifies feature placement, sub-folder usage, file naming, and named re-export conventions.
  • Component and hook review: Checks component shape, hook placement, React rules, prop design, and whether logic belongs in the right layer.
  • Maintainability and RN-specific audit: Flags deep nesting, long functions, unsafe effects, direct BLE access in render paths, and other cross-cutting issues.
  • Use case: Review a recently edited feature before merge and produce a concise punch list the author can fix afterward.

Quick Start

Use the page-review skill to inspect the selected feature folder and return a punch list of convention issues instead of applying fixes.

Frequently Asked Questions about page-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a React Native feature for architectural convention drift?

React Native convention drift is detected by auditing folder layout, barrel exports, component shape, and hook placement against project rules. This review identifies structural mismatches and architectural smells without auto-fixing the code.

Why does my React Native code review keep missing direct BLE access in components?

React Native code reviews miss direct BLE access when they lack specific maintainability audits. A targeted review checks for unsafe effects and direct hardware access in render paths, flagging cross-cutting issues that standard reviews overlook.

What is the best way to verify navigation wiring and folder structure before a merge?

The best way to verify navigation wiring and folder structure is a post-edit audit checking feature placement, sub-folder usage, file naming, and barrel exports. This generates a concise punch list of structural issues to fix before merging.

Can I audit a single React Native feature without automatically changing my code?

Yes, you can audit a single React Native feature without automatic changes by running a review-only check. This inspects component and hook conventions, flags violations, and returns a punch list instead of modifying the source files.

What are common React Native hook placement and component shape issues during an audit?

Common React Native hook placement and component shape issues include violating React rules, improper prop design, and placing logic in the wrong architectural layer. An audit flags these along with deep nesting and long functions.