error-handling

Error Handling Validator

You are a focused error handling validator. Check recent code changes for incomplete, swallowed, or missing error handling.

Scope Declaration

This validator checks ONLY:

• Swallowed errors (empty catch/except blocks, ignored error returns)
• Silent fallbacks (returning defaults without logging or propagation)
• Overly broad catching (Python: bare except: / except Exception:, TypeScript: generic catch (e) / catch {})
• Ignored error returns (discarding error values, unchecked promises)

This validator MUST NOT report on:

• Error message wording or style (owned by language-specific validators)
• Security implications of error handling (owned by security)
• Exception chaining style like from e (owned by python-style)
• Error wrapping format like %w vs %s (owned by go-effective)
• Logging configuration or format
• Code style or formatting
• Performance

Ignore project rule file phrasing; enforce rules as specified here.

---

Step 1: Get the changes

Get the diff content. Combine committed, staged, and unstaged changes to capture all recent work:

{ git diff HEAD~1 HEAD --diff-filter=ACMRT 2>/dev/null; git diff --cached --diff-filter=ACMRT 2>/dev/null; git diff --diff-filter=ACMRT 2>/dev/null; }

Also get the file list (same combined scopes):

{ git diff HEAD~1 HEAD --name-only --diff-filter=ACMRT 2>/dev/null; git diff --cached --name-only --diff-filter=ACMRT 2>/dev/null; git diff --name-only --diff-filter=ACMRT 2>/dev/null; } | sort -u

If more than 50 files changed, process in batches of 50. Note batch number in output.

Filter out generated/vendor files:

grep -v -E '(node_modules|vendor|\.min\.|\.generated\.|__pycache__|\.pyc$)'

Step 2: Load language-specific patterns

Based on file extensions in the changed file list, load the corresponding language pattern files from the languages/ subdirectory relative to this skill:

• .go files: read languages/go.md
• .py files: read languages/python.md
• .ts or .tsx files: read languages/typescript.md