Results for “console-errors”

Use this skill for browser verification, console/network errors, layout checks, user-flow QA, DevTools evidence. Trigger when the task involves qa work related to Browser Devtools Qa, production implementation, audits, debugging, strategy, or validation.

Systematic debugging workflow for errors and bugs. Use when debugging errors, investigating bugs, troubleshooting issues, or when something isn't working as expected. Integrates Sentry MCP for production error context, Firecrawl for researching fix patterns, and Sequential Thinking for complex multi-step diagnosis.

跨 TypeScript、Python、Go 的健壮错误处理模式——涵盖类型化错误、错误边界、重试策略及优雅降级

Identify error-prone APIs and dangerous configurations

Audit a codebase for silent failures, swallowed exceptions, and observability gaps across Sentry and Langfuse, then produce a phased fix plan. Use when the user says "errors aren't showing in Sentry", "things fail silently", "empty catch blocks", "add error handling", "check my Langfuse tracing", or is hardening.

Handle errors as values using fp-ts Either and TaskEither, replacing try/catch with predictable, type-safe error handling patterns.

Windows Console Unicode Compatibility

Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Provides patterns for robust error handling across TypeScript, Python, and Go, including typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

Full automated QA suite — visual design review + UAT functional testing. Screenshots every viewport, analyzes against Nick's design system, then runs functional UAT (navigation, links, forms, buttons, auth flow, accessibility, performance, console errors, responsive testing). Use after every deployment.

Assemble a Jira/Linear/GitHub-Issue body from recent commits, diff, and branch context

Fix CI failures by fetching GitHub Actions logs, dispatching dev to fix, verifying locally, and pushing.

This skill should be used when encountering authentication errors, API key errors, 401 errors, "invalid API key", "BANKR_API_KEY not set", job failures, or any Bankr API errors. Provides setup instructions and troubleshooting guidance for resolving Bankr configuration issues.

Error Handling — Agent Arena

Error handling review — silent failure detection, catch block analysis, error logging.

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

API Security (Verbose)

Identify and exploit Cross-Origin Resource Sharing misconfigurations that allow unauthorized cross-domain data access and credential theft during authorized security assessments.

Investigate and fix bugs, crashes, null references, and runtime errors in QuizVerse.

Provides patterns for robust error handling across TypeScript, Python, and Go, covering typed errors, error boundaries, retries, circuit breakers, and user-facing messages.

Local build-error triage. Detects common compile errors and suggests fixes

Scans modified files for debug leftovers before shipping. Catches console.log, debugger, test URLs, and commented-out code.

Build Error Fix Skill

Design error prevention, detection, and recovery experiences that minimize user frustration.

Configure CORS for web APIs. Use when a user asks to fix CORS errors, allow cross-origin requests, configure CORS headers, handle preflight requests, or secure API access from different domains.

Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

Trigger: empty list state, loader skeleton, error boundary layout, offline indicator, system fallback UI. Scope: UI fallback layouts, skeleton placeholders, client recovery views. Boundary: Excludes server-side API error status coding.

Diagnoses pipeline failures, schema validation errors, ffmpeg crashes, and API errors, then attempts safe automatic recovery.

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

OS command injection occurs when user input is passed unsanitized to a system shell via dangerous APIs: Java `Runtime.exec()`, Python `os.system/subprocess`, PHP `system/shell_exec/exec/proc_open`, C `system/exec`. Detect via pipe `|`, semicolon `;`, `&&`, `||`, backtick, `$()` operators, and time-delay payloads (`sleep 5`). Tools: Commix, Burp Suite, OWASP WebGoat.