Set up or review production error monitoring to capture unhandled errors, failed requests, and performance signals. Check event context, release labels, and alert routing so teams receive useful information when problems occur.
Use when setting up a new project's production observability stack, reviewing incident response readiness, or investigating why errors are going undetected.
Run score Not tested
See how to installThis skill sets up monitoring to collect errors from a production app and support investigation and alerts. For configurations using SDKs from services such as Sentry, Datadog, or Bugsnag, it checks unhandled exceptions, Promise rejections, framework errors such as those in React, and failed network requests. It also reviews attached user information, release versions, and environments, along with alert thresholds and contacts for serious errors.
Use it when preparing production monitoring for a new project or reviewing incident response arrangements. If errors do not reach the monitoring service, it examines initialization, overly broad filters, and code that swallows errors along the way. Its scope also includes measurements from actual usage and Core Web Vitals, metrics related to the experience of using a page.
Monitoring requires an error monitoring service such as Sentry, Datadog, or Bugsnag, together with integration of its SDK.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Production errors are invisible without monitoring. Users rarely file detailed bug reports — they simply leave. Error monitoring gives you actionable stack traces, breadcrumbs, and user context within seconds of an issue occurring, cutting mean time to detect (MTTD) from days to minutes and dramatically reducing the cost of incidents.
Check whether an error monitoring service is configured and capturing unhandled errors, promise rejections, React/framework-level errors, failed network requests, and production Core Web Vitals signals.
Integrate an error monitoring SDK, configure environment and release tagging, capture failed network requests and RUM metrics, and set up alerts for critical error thresholds and regressions.
Explain how error monitoring services work, what signals they capture, and how error grouping reduces alert noise.
Review the monitoring initialisation code. Flag missing user context, absent release tagging, overly broad event filters, missing network instrumentation, and any patterns that would swallow errors before they reach the monitoring service.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/testing/error-monitoring
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.