Skip to content

Error Handling Reviewer

Reviews JavaScript code for proper try-catch, promise rejection, and React error boundary use

Stars
74,632
Licence
MIT
Files
2 files

What it does

Once installed, the agent reviews JavaScript code, components, and browser behaviour for error handling gaps, such as async calls without try-catch, errors swallowed silently, or missing React Error Boundaries. It also suggests fixes that add proper handling and logging, and explains best practices. The skill is a set of written guidelines and checklists; the files provided contain no executable scripts.

Great for

  • Front-end developers who want a second look at async code and error paths before release
  • Teams reviewing React components for missing Error Boundaries
  • Students learning JavaScript error handling patterns

Skip it if

  • Projects needing a runtime test or automated check: the skill only guides review, it does not run tests or verify behaviour in a browser
  • Non-JavaScript stacks, since the guidance is specific to JavaScript and React

Try asking

  • “Review this fetch-based component and tell me where async errors are not handled”
  • “Add try-catch and logging to these async functions in my checkout flow”
  • “Explain when I should use a React Error Boundary versus local error state”
Step-by-step guide: how to use Error Handling ReviewerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    error-handling.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip error-handling.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip error-handling.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Point the agent at specific files or components so the review stays focused
  • Ask it to state how each fix should be verified in the browser, as the skill's Code Review section asks for
  • Check the referenced rule page for framework-specific examples, since the skill itself is brief

What's inside

  • references/rule.md
  • SKILL.md

Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.