Index of every page on this site: llms.txt
All skills
neha avatar

/code-review

@eb9f097
Run it yourself

Audit entry point for reviewing React Native code. Applies crash and data-loss rules on every change, and opens a focused skill only when the diff touches that concern.

Use this Skill: https://skilld.dev/gh/neha/rn-developer-skills/code-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈45 tokens for metadata: the name and description. ≈1.4k when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈182 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Code Review Skill

Applicability

  • Platforms: iOS and Android
  • React Native: 0.76+ (New Architecture interop assumed unless a checklist item says otherwise)

When to Use

  • Reviewing a pull request or code change
  • Auditing an existing screen or feature for issues
  • Running a pre-merge quality gate
  • Investigating the root cause of a production bug

This skill is the entry point for a review. It does not restate every check. Apply the steps below, then report findings in the output format.

Prerequisites

  • Access to the code being reviewed
  • An understanding of the feature's intended behaviour
  • Knowledge of which data is user-sensitive or business-critical

How to Conduct a Review

  1. Always apply critical-rules, and only to lines this diff adds or edits. A crash on a line the diff does not touch is out of scope. Put a pre-existing issue in Consider only when it sits on a line the diff edits.
  2. Apply conventions when the diff adds or renames files, or changes structure or types. Skip it for a behaviour-only edit inside an existing file. Conventions findings are should-fix, not merge-blocking.
  3. Open another skill only when the diff touches that concern. Read that skill's Severity section before you promote a finding to Must-Fix.
  4. List the skills you did not open in one line under Not applicable. Do not write a line per skill, and do not paste a checklist.
Concern Open it when the diff… Focused Skill
Spec is a new feature and the spec is part of the review. A missing spec is Consider, not a merge block spec-authoring
Architecture adds a screen, changes navigation, layout, or deep-link lifecycle architecture
Performance changes a list, image, animation, or a screen that drops frames performance
Accessibility adds or changes an interactive control, label, or focus accessibility
Testing changes behaviour a user or caller can observe testing
State & Data changes a request, cache, offline path, or transaction state-and-data
Security touches auth, secrets, PII, payments, consent, or which link target is allowed security
Native integration touches permissions, native modules, or background work native-integration
Forms touches inputs, validation, the keyboard, or submit forms-and-validation
Observability touches logging, analytics, or crash reporting observability
Localization adds user-facing copy, locale formatting, or RTL layout i18n-and-localization
Error handling adds a screen, a failure path, or retry error-handling
Notifications touches push or local notifications notifications
Theming changes colours, dark mode, or theme tokens theming
Upgrades bumps React Native or a native dependency upgrades
Release changes a store build, version, or over-the-air bundle release-and-updates

Incorrect: a review that files {count && <Text>} when that line is not in the diff, or that writes a "not applicable" line for every skill.

Correct: a review that runs critical-rules on the changed lines, opens forms-and-validation because the diff changes a form, and ends with one line: "Not applicable: performance, notifications, upgrades, release."

Output Format

Structure every review as:

  1. Summary — overall assessment (solid / needs work / significant issues)
  2. Must-Fix — crashes, data loss, or a security issue in code this diff touches (block merge)
  3. Should-Fix — performance, architecture, or missing tests for the behaviour this diff changes
  4. Consider — alternative approaches, future-proofing, style
  5. What's Good — well-implemented patterns worth reinforcing

Name the skill each finding comes from. Say which concerns are not applicable.

Worked Example

Diff, and only these lines:

{password.length && <Text>{password.length} characters</Text>}
<Button
  disabled={password.length === 0}
  title="Log in"
  onPress={submit}
/>

No test was added. The button already had a visible label.

Summary: Needs work. The disabled check is right. The new character count uses &&.

Must-Fix:

  • critical-rules: {password.length && <Text>} is in the diff. A length of 0 is falsy. Use password.length > 0 &&.

Should-Fix:

  • accessibility: this diff sets disabled and does not set accessibilityState={{ disabled: password.length === 0 }}.
  • testing: this diff changes when the button enables and adds no test for that.

Not applicable: spec-authoring, architecture, performance, state-and-data, security, native-integration, observability, i18n-and-localization, error-handling, notifications, theming, upgrades, release-and-updates.

Consider: none. The empty-password message on an unchanged line stays out of this review.

What's Good: disabled uses password.length === 0, so an empty password cannot submit.

Pitfalls

  • Opening every focused skill on a small diff produces noise, and the real crash gets lost.
  • Restating a focused skill's checklist here causes drift. Keep the detail in that skill.
  • Skipping "What's Good" removes the part of a review people remember.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    The skill provides a structured framework for conducting React Native code reviews. It contains no malicious code, obfuscation, or data exfiltration patterns. It defines a workflow for auditing diffs using focused sub-skills.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

Signed by skilld at eb9f097. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
version
3.1.0
platforms
[
  "ios",
  "android"
]
react-native-version
0.76+
Other metadata
tags
[
  "react-native",
  "code-review",
  "audit"
]

README badge

README badge for neha/rn-developer-skills/code-review