agentleFS
Sign inStart free
sagawrrsagawrr/skills/rn-review/SKILL.md

rn-review

Skill0 starsChanged 5 months agoMITView on GitHub

Reviews a React Native or Expo PR diff for code-level correctness, performance anti-patterns, and AI-era defects. Outputs findings ranked by severity with file:line citations. Use when asked to review a PR, audit a diff, or check code before merging. Specifically tuned for patterns that look correct but break at runtime on New Architecture or under wrong library versions.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always load: checklist §1 (New Architecture), §4 (useEffect), §6 (Type Safety), §7 (Bundle), §8 (Expo Router), §10 (AI Bloat).

    line 20
  2. Distinctive:

    Start with a one-line verdict, then counts, then findings grouped by severity.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

React Native PR Review

Reference Loading

Before starting the review, read package.json and load only the relevant reference sections:

If package.json contains…Load these checklist sections
react-hook-formchecklist §11 (RHF + Zod)
reanimatedchecklist §2 (Reanimated 4)
nativewindchecklist §9 (NativeWind)
@tanstack/react-querychecklist §3 API version items
@shopify/flash-listchecklist §5 (List Rendering)

Always load: checklist §1 (New Architecture), §4 (useEffect), §6 (Type Safety), §7 (Bundle), §8 (Expo Router), §10 (AI Bloat).

Load references/ai-patterns.md only if the diff shows clear AI-generated patterns (god components, speculative memoization, what-comments) or for first-time review of an AI-heavy codebase.

How to Run

/rn-review           # reviews current git diff
/rn-review --fix     # applies safe mechanical fixes (BLOCKER + HIGH)
  1. Get the diff: git diff main...HEAD
  2. Scan each checklist category from references/checklist.md against the diff
  3. Cite every finding as path/file.tsx:line — [SEVERITY] description + fix
  4. Output ranked summary: BLOCKER → HIGH → MEDIUM → INFO

Severity

LevelMeaningExample
BLOCKERRuntime crash, data loss, broken on New ArchitectureonSuccess in useQuery v5
HIGHSilent regression, wrong API, perf degradationref without collapsable={false}
MEDIUMMaintainability, suboptimal patternspeculative useMemo
INFOBetter alternative existssuggest scheduleOnRN over runOnJS

Checklist Categories (run in parallel)

Each category is detailed in references/checklist.md:

  1. New Architecture — batching, refs, shadow props, Fabric APIs
  2. Reanimated 4 — animated properties, scroll handler, worklet safety
  3. API version correctness — TanStack Query v5, FlashList v2, SDK 55+ changes
  4. useEffect audit — every useEffect needs a justification
  5. List rendering — FlashList setup, recycling keys, item stability
  6. Type safety — any, type assertions, missing return types
  7. Bundle — barrel imports, Platform.OS vs process.env.EXPO_OS
  8. Expo Router — file placement, layout files, navigation API
  9. NativeWind — v4/v5 mismatch, cascade assumptions, dark mode
  10. AI bloat — over-abstraction, god components, comment noise, speculative memoization

Output Template

Start with a one-line verdict, then counts, then findings grouped by severity. Example:

## RN Review — shipping risk: HIGH · 1 BLOCKER · 2 HIGH · 1 MEDIUM

### BLOCKER
- `src/screens/Feed.tsx:42` — `onSuccess` in `useQuery` removed in TanStack Query v5.
  Fix: move to `useMutation.onSuccess` or a `useEffect` watching `data`.

### HIGH
- `src/components/Card.tsx:18` — `<View ref={cardRef}>` without `collapsable={false}`.
  New Architecture view flattening makes this ref always null.
  Fix: `<View ref={cardRef} collapsable={false}>`

- `src/screens/Home.tsx:55` — `useEffect(() => setFiltered(items.filter(fn)), [items])`.
  Derives state in an effect. Compute `filtered` during render instead.

### MEDIUM
- `src/hooks/useData.ts:12` — `useCallback` with empty deps. React Compiler handles this — remove.

Shipping risk = BLOCKED (any BLOCKER) · HIGH (any HIGH) · MEDIUM (MEDIUMs only) · CLEAN (INFO only or none).

Omit severity levels with zero findings. Skip INFO unless it's the only finding.

References

  • references/checklist.md — full itemized checklist per category
  • references/ai-patterns.md — AI-era defect patterns with ❌/✅ examples
  • Related: expo-react-native skill (authoritative patterns reference)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free