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

/observability

@eb9f097
Run it yourself

Review React Native crash reporting, breadcrumbs, performance traces, and analytics for PII-safe production debugging. Use when adding monitoring or reviewing observability in a change.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈50 tokens for metadata: the name and description. ≈868 when used: this file.

Description uses 2.5% 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 ≈201 characters, or 2.5%.

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.

Observability Skill

Applicability

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

When to Use

  • Adding crash reporting, analytics, performance traces, or a logging strategy
  • Reviewing what a change records about the user or the session
  • Debugging a production failure that cannot be reproduced on a device

Severity

  • Merge-blocking: a new event or log in this diff includes a name, email, token, or payment data.
  • Should-fix: missing traces and breadcrumb wording.

Guidance

Names, emails, and payment data in logs are also merge-blocking under critical-rules. File that finding once, from critical-rules, when the line is in the diff.

Crashes and errors

  • Uncaught JavaScript errors, unhandled promise rejections, and native crashes are reported, and release builds can be symbolicated
  • An error boundary reports the screen it failed on and still shows a recovery UI
  • Caught errors that the user can retry are not also reported as crashes
  • Dev and debug builds do not send events to the production project

Context

  • Breadcrumbs record the action (screen opened, request failed) without the payload
  • A correlation id is attached to the client event and the matching server request
  • User id, when set, is an internal id, not an email, name, or phone number
  • Events are separated by environment (dev, staging, production)

Incorrect:

logger.error('checkout failed', { email, cardLast4, token });

Correct:

logger.error('checkout failed', {
  correlationId,
  screen: 'Checkout',
  status: error.status,
});

Performance

  • Screen-load and API-latency traces exist for the flows that matter, with a start and an end
  • A trace is cancelled or dropped when the screen unmounts before it finishes
  • JS-thread stalls are sampled; they are not logged on every frame

Analytics and privacy

  • Event names are stable and documented; properties follow one schema
  • No names, emails, payment data, tokens, or free-text user content are in events or logs
  • Collection starts only after the required consent (see security)
  • Offline events are queued with a cap and are not sent with a payload captured before consent

Anti-Patterns

Anti-Pattern Risk Fix
Logging the request body PII and tokens land in a vendor log Log status, route template, and correlation id
A catch that reports and also swallows The user sees a success while the crash tool fills with noise Show the error, and report only unexpected failures
One analytics name reused for different actions Funnels lie One name per action, with a written schema
Sending debug logs to the production project Dev traffic hides real crashes Split the project or the environment tag and drop dev

Pitfalls

  • Release crashes without source maps or native symbols point at minified frames. Confirm symbol upload for the build that shipped.
  • A high sample rate on a chatty trace (scroll, animation) can drain battery and blow the quota. Sample those; keep crashes unsampled.
  • Offline queues replay old events after the user logs out. Drop or re-key the queue on sign-out.
  • Breadcrumbs that include search text or form values become a second store of personal data. Keep them to navigation and outcomes.

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 set of guidelines and checklists for an AI agent to review React Native code for observability, crash reporting, and analytics. It specifically focuses on preventing the exposure of PII (Personally Identifiable Information) in logs and events. No executable code, remote dependencies, or malicious patterns were found.

  • 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
1.0.1
platforms
[
  "ios",
  "android"
]
react-native-version
0.76+
Other metadata
tags
[
  "react-native",
  "observability",
  "crashes",
  "analytics",
  "privacy"
]

README badge

README badge for neha/rn-developer-skills/observability