'error' 검색 결과

Handle merged cells before filling Excel templates with openpyxl, a Python library for spreadsheets. This skill shows how to inspect merged ranges, unmerge the required areas, write values, and save the workbook without merged-cell write errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fill an Excel template containing merged cells
• Resolve AttributeError when writing cell values
• Unmerge ranges across multiple worksheets

Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Monadic types for Golang using samber/mo — Option, Result, Either, Future, IO, Task, and State types for type-safe nullable values, error handling, and functional composition with pipeline sub-packages. Apply when using or adopting samber/mo, when the codebase imports `github.com/samber/mo`, or when considering functional programming patterns as a safety design for Golang. Not for nil-safety and zero-value design without this library (→ See `samber/cc-skills-golang@golang-safety` skill), nor for native error wrapping with fmt.Errorf, errors.Is and errors.As (→ See `samber/cc-skills-golang@golang-error-handling` skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: "agent not working", "wrong answer", "agent error", "tool call failing", "debug agent", "check logs", "read traces", "broken", "500 error", "424 error", "model access denied", "command not found", "stuck in DELETING", "maxVms exceeded", "cold start diagnosis", "cold start slow", "agentcore create error", "create failed", "exit code 7", "connection refused local dev". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize. Not for VPC configuration — use agents-build. Not for observability setup or missing logs — use agents-optimize.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cross-cutting standards for error design, response shapes, error codes, and boundary placement across API, domain, and infrastructure layers. Use when defining error hierarchies, wrapping exceptions, building standardized error responses, or placing error boundaries in layered architectures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fix flaky Flutter/Dart tests that fail in CI but pass locally due to unhandled Future rejections. Use when: (1) Test passes locally but fails in CI with cryptic errors, (2) Test creates Futures that will throw errors (e.g., network calls to fake URLs), (3) Even with .catchError() at the end, test still fails, (4) Error message shows test name but truncated error like "ROR]" or "[ERROR]". Solution: Avoid creating Futures that will reject; test state machine behavior with synchronous operations instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead, timeout), error budgets/SLOs with burn rate alerts, and production incident triage. Use when user asks to implement error handling, logging, monitoring, observability, OpenTelemetry, error boundaries, circuit breakers, retry logic, or SLO tracking. Do NOT use for incident runbooks (use runbook-gen), vendor-specific APM setup (Datadog, Sentry agent config), or K8s debugging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MCP skill for IGW (InsurGateway) error management — list, analyze, report, and manage insurance integration errors across test and production environments. Invoke whenever user asks about IGW errors, insurance gateway issues, success rates, or error reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build error triage: detect language, load fix patterns, auto-retry. Use for 'build failed', 'fix compilation', 'type error'. Chains into mk:verify. NOT for runtime errors (see mk:fix); NOT for architectural debugging (see mk:investigate).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates consistent error handling with custom error classes, HTTP status mapping, structured logging, safe client messages, and error taxonomy. Use when standardizing "error handling", "logging", "error responses", or "exception management".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rust 코드를 작성·검토·개선하며 소유권, 오류 처리, 타입 설계와 동시성을 정리합니다. 안전성, 성능, 유지보수성을 고려한 구현을 돕습니다.

• Rust 소유권과 빌림 검토
• 오류 발생 시 중단되는 처리 개선
• Rust 앱의 타입과 모듈 설계

라우터, 스위치, Linux의 통신 오류와 연결 끊김을 조사합니다. 링크 양쪽 설정과 오류 증가량을 비교해 케이블 불량이나 혼잡 등의 원인을 좁힙니다.

• 통신 끊김과 패킷 손실을 조사합니다
• 스위치의 CRC 오류 증가를 조사합니다
• 링크 양쪽의 설정을 비교합니다

Review how a website behaves when images fail to load and add fallback images or meaningful placeholder content. Check loading behavior, consider loading placeholders, and use error logging and browser developer tools to investigate and verify fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding fallback images for broken image links
• Reviewing placeholders shown while images load
• Investigating image loading failures with logs and DevTools

Build cryptocurrency exchange integrations in Rust with CCXT. Follow examples for fetching prices and order books, placing orders, streaming live updates through WebSocket connections, and handling authentication and errors with typed results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fetching exchange prices and order books in Rust
• Building order placement and cancellation workflows
• Streaming live prices through WebSocket connections

Write integration tests for core error processors by simulating API failures with a mock model. Check retry attempts, changes to conversation messages, and streamed responses, with guidance on test setup and diagnosing empty output.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check retries and message changes after API errors
• Diagnose empty output in streaming tests
• Verify unrelated errors pass through unchanged

Reproduce model connection failures and interrupted responses in the desktop app using a local fault server and test providers. Check error messages and retry behavior for refused connections, DNS failures, HTTP errors, stalled requests, and cut streams.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking error messages for model connection failures
• Testing responses to rate limits and server errors
• Reproducing stalled requests and interrupted replies

Reproduce chat errors, retries, parallel tool calls, and app creation in a running desktop application. Check how messages and cards appear, including interrupted replies, grouped steps, and error details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check error messages and retry progress
• Inspect text retained after an interrupted reply
• Review grouped parallel tool calls

Diagnose iii invocation failures using error codes across Node, Python, Rust, and browser workers. Distinguish permission denials, timeouts, and handler failures, then choose appropriate exception handling and decide whether retrying is suitable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Diagnosing failed function calls by error code
• Deciding whether a timed-out operation should be retried
• Handling permission denials without blind retries

Write, review, and debug Rust applications, including ownership and borrowing rules that govern memory use. Covers trait-based APIs, explicit error handling, asynchronous work with tokio, and tests with Cargo validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Resolve ownership, borrowing, and lifetime errors
• Design APIs with traits
• Implement asynchronous tasks with tokio

Investigate errors, crashes, and unexpected behavior by reproducing failures, tracing execution, and comparing logs. Tests one explanation at a time, then provides a verified fix, supporting evidence, and tests or safeguards to prevent recurrence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate error messages and execution traces
• Find the cause of an application crash
• Compare logs to locate a failure

Capture production errors from Convex server functions and browser interfaces in your own deployment. Redact sensitive information before storage, inspect recent failures, monitor new events, and optionally route recurring errors into a workflow that opens fix pull requests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Collect server and browser errors in one deployment
• Inspect production failures with sensitive details redacted
• Monitor newly recorded errors

Wait for the next Convex development error, production error, or feature request, then respond with investigation, a fix, or implementation. The skill combines local logs and deployment events, using polling when blocking tools are unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Waiting for the next error during development
• Investigating and fixing newly detected production errors
• Starting implementation when a feature request arrives

Run TypeScript type checks when standard commands fail, then filter diagnostics to files involved in your task. Preserve the compiler’s exit status while reviewing relevant errors separately from existing project errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running type checks when npx tsc fails
• Reviewing diagnostics for newly created files
• Filtering errors to a feature directory

Check whether a file creation or transformation task actually succeeded after an unclear execution error. Inspect output files and their contents to distinguish success, partial completion, and failure before deciding whether to retry.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking output files after an unknown error
• Validating spreadsheet or JSON contents
• Deciding whether to retry or fix incomplete output