Results for “compilation-errors”

Build Error Fix Skill

Fix CuPy NVRTC compilation errors on Windows. Trigger: NVRTC_ERROR_BUILTIN_OPERATION_FAILURE, nvrtc-builtins64 not found

Provides a structured triage process for debugging test failures, build errors, runtime bugs, and production incidents, including steps to reproduce, localize, fix, and guard against recurrence.

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

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

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

Audit a repo (or diff) for weak error handling — swallowed exceptions, bare catches, unhandled promise rejections, missing network timeouts/retries, and errors logged but not surfaced. Pure Claude Code, no MCP, no signup.

Analyzes .NET Framework CLR activation logs to diagnose runtime loading failures, version selection issues, and Feature-on-Demand dialog behavior.

Fix MSBuild targets so generated files are compiled, copied to output, and cleaned properly.

Diagnose MSBuild build failures by analyzing .binlog files using an MCP server or text-log replay.

Detects and fixes common MSBuild anti-patterns in .csproj, .vbproj, .fsproj, .props, .targets, and .proj files, covering Exec misuse, unquoted conditions, hardcoded paths, and more.

Iterate on a pull request until actionable CI checks pass and high/medium review feedback is addressed, stopping at human approval, draft, or merge gates.

Remove assigned mypy exclusion modules in small batches, fix typing issues, run validation, and produce a structured completion summary.

Build clean async pipelines with fp-ts TaskEither, replacing nested try/catch with composable error handling and real API examples.

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

Diagnose and fix failing CircleCI builds quickly and safely. Use when users ask to investigate failed CircleCI jobs, triage flaky pipelines, identify root causes from logs, and implement minimal fixes in configuration, test setup, or build-related code paths.

Use when the team needs a strategy for validation errors, API failures, job retries, user-facing error UX, observability, or recovery behavior. Trigger on requests to design error handling across frontend, backend, and integrations.

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.

Structured troubleshooting for Sage/Acorn/Lando projects — diagnoses PHP errors, Blade rendering failures, Livewire mount errors, Eloquent query issues, Acorn boot failures, queue job failures, WP hook conflicts; uses lando logs, Query Monitor, Xdebug, WP_DEBUG. Invoke for: "/debugging", "something is broken and I can't figure out why", "lando logs show an error", "acorn boot error", "blade is rendering wrong", "livewire component not mounting", "500 error", "debug this issue". Skip when: you are building or implementing features — that is /building, not debugging.

Automates the cycle of fixing CI failures, addressing PR review feedback, and pushing changes until all checks pass.

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.

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

Runs a comprehensive verification pipeline for Quarkus projects including build, static analysis, tests with coverage, security scans, native compilation, and diff review before PRs or releases.

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

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

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Diagnoses and fixes build, type, and runtime errors with minimal changes, covering TypeScript, PyTorch, and other build systems.

Patterns for debugging and extending the AegisNex GitHub Actions CI pipeline. Covers common failure modes, encoding issues, dependency problems, and how to add new CI steps.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Use when compiling a LaTeX paper, debugging LaTeX errors, building a paper PDF, or when a .tex file fails to produce output. Handles engine detection (xelatex vs pdflatex), bibliography systems (biber vs bibtex), and multi-pass compilation.

Diagnose failures from runtime evidence before editing code.

Error Handling Patterns

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

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