Development
New
$15.00Python Performance Audit
Audit Python latency, CPU, memory, I/O, and throughput with reproducible profiles, controlled experiments, correctness checks, and regression gates.
pythonperformance
V
vareno
Updated Jul 16, 2026
Configure and verify Sentry for React Native and Expo with privacy boundaries, release identity, source-map proof, controlled tests, and a clean handoff.
A Sentry SDK can be installed and still leave the useful part of error monitoring broken. Events may reach the wrong project. Source maps may belong to another build. A JavaScript test can pass while native crashes remain unreadable. A broad copy-pasted setup can also collect more data than the team intended.
Sentry React Native Setup starts by freezing the app revision, Expo or bare React Native path, platform versions, existing Metro and navigation configuration, build provider, environments, and authority boundary. It separates the client DSN from build-time credentials and keeps personally identifiable information, tracing, replay, profiling, screenshots, logs, and other optional collection out of scope unless they are explicitly approved.
The workflow checks the installed stack against current Sentry, Expo, and build-provider support before proposing code. It produces a bounded change matrix for initialization, config plugins or native integration, Metro composition, routing, build profiles, secrets, source-map and native-symbol uploads, rollout, and rollback. Existing app behavior is preserved instead of being replaced with a minimal example.
Verification binds the repository commit to the build, release, distribution, JavaScript bundle and source map, native debug identifiers, upload result, and received event. JavaScript errors, native crashes, render failures, and API failures have separate gates. An upload timeout stays unknown until read-back distinguishes no effect, partial effect, conflict, verified effect, or unavailable evidence; it is never a reason for a blind retry.
The package includes a setup-record contract and a read-only structural checker for machine-checkable handoffs. It cannot authenticate Sentry or a build provider, approve privacy policy, create secrets, upload artifacts, trigger crashes, ship a build, or prove production behavior without the relevant access, authority, and evidence.
Version 1.0.0 was evaluated on 27 July 2026 with Codex CLI and gpt-5.6-sol in 12 fresh read-only contexts. Across three blind comparison cases, the candidate scored 100, compared with 83.33 for the same agent without the skill and 77.5 for the exact free upstream. It passed every case and led the comparison arms by 16.67 and 22.5 points overall. The cases covered an Expo privacy-scoped design, an ambiguous EAS source-map upload, and a partial-coverage release gate. This evaluation measures those supplied cases; it does not prove that a real app or Sentry project was changed.
The reviewed package SHA-256 is 259e169c162429a6107561a9ef41bdc2d27a5fe5c174b2da2bb42c469bdb43dd. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
Expo 55, React Native 0.82, Expo Router, Hermes, custom Metro config, and EAS preview and production profiles. Design only. Error monitoring is approved, but tracing, replay, screenshots, and default PII are not.
Output
A frozen target, current-support checks, bounded config and initialization matrix, preserved Metro and router behavior, secret and data boundaries, release and artifact identity plan, separate iOS and Android verification gates, rollback, and a design-ready handoff without claiming execution.
Input
An EAS Android build completed, the upload command timed out, two logs disagree about the distribution, and the only Sentry event still shows bundle.js frames. Review and repair plan only.
Provide the repository revision, Expo or React Native path, installed versions, entry point, Metro and navigation setup, build profiles, Sentry project target, desired error coverage, privacy rules, current evidence, and separate permission to inspect, edit, build, upload, test, deploy, or roll back. Ask for a setup design, existing-configuration review, source-map reconciliation, controlled verification plan, repair proposal, or operational handoff.
Repository revision, Expo managed or bare React Native path, installed SDK and tool versions, platforms, entry point, Metro and navigation setup, build provider, profiles, and environments.
Organization and project target without credentials, region or base URL, existing initialization and uploads, plus the approved JavaScript, native, render, API, tracing, replay, profiling, or logging scope.
Approved data classes, PII default, sampling, retention, residency, access, deletion, DSN treatment, auth-token owner, and protected secret storage.
Observed configuration, build and upload records, event IDs or failures, and separate permission to inspect, edit, install, manage secrets, build, upload symbols, trigger tests, deploy, change sampling, or roll back.
SKILL.md; Sentry setup-record contract; read-only setup-record checker; Codex interface metadata
No reviews yet.
Output
An unknown-state record, complete build-to-event identity chain, current setup assessment, read-back branches for no effect, partial effect, conflict, verified effect, or unavailable evidence, and a bounded repair rule that never repeats an unproven upload.
Input
Unhandled JavaScript events arrive, but there is no controlled native crash evidence, source identifiers are missing, the API capture may include query strings, and no release owner has approved production tests.
Output
A verification-incomplete verdict, explicit setup and compatibility gaps, separate JavaScript and native gates, artifact-binding requirements, sensitive-field inspection, owner decisions, safe fixtures, rollback conditions, and one bounded next action.
Creator
Jjovaro1