Review JavaScript JSON parsing for malformed input and unexpected data structures. Add error handling and validate parsed data before use, helping prevent failures when reading API responses, browser storage, or user-provided content.
Use when reviewing scripts, client components, bundles, or runtime behavior related to Parse JSON safely with error handling. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
This skill reviews JavaScript JSON parsing and adds handling for malformed input and unexpected data structures. It finds JSON.parse() calls and checks whether try/catch handles exceptions and whether the parsed structure is validated before use. It identifies and fixes specific problems in code that reads API responses, values saved in localStorage, or data entered by users.
Use it when malformed JSON stops the page from working, or when missing properties cause errors later in the code. It also helps during code reviews when you want to check how external data is received and used. The review covers both parsing errors and problems with the structure of data that parses successfully.
JSON.parse() calls in this file and add exception handling and data structure validation.”Successful JSON parsing and a valid data structure are checked separately. The source mentions Zod and Valibot for validating external data, but installing a particular library is not a requirement.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. 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.
JSON.parse() on invalid input throws a SyntaxError that will crash your application if uncaught. API responses, localStorage values, and user-provided data can all be malformed. Safe parsing with validation catches these errors at the point of parsing, not deep in your application logic when a missing property causes an unexpected error.
Find all JSON.parse() calls in this file and check whether each one is wrapped in try/catch and whether the result is validated before use.
Add try/catch error handling to all JSON.parse() calls and add shape validation to protect against unexpected data structures.
Explain why JSON.parse can throw, what safe JSON parsing looks like, and when to use schema validation libraries.
Review scripts, client components, and browser execution paths related to Parse JSON safely with error handling. Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/javascript/json-safety
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.