「failures」の検索結果

Recover from execute_code_sandbox failures by writing Python scripts to files and executing via run_shell

日本語の概要は準備中です。原文の説明を表示しています。

Debug Python script execution failures by capturing full output with exit codes and verifying working directory before file operations

日本語の概要は準備中です。原文の説明を表示しています。

Four-step recovery workflow for code execution failures when inline Python fails

日本語の概要は準備中です。原文の説明を表示しています。

Handle web research failures with explicit error recognition and domain-specific fallback strategies

日本語の概要は準備中です。原文の説明を表示しています。

Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge

日本語の概要は準備中です。原文の説明を表示しています。

Handle web research failures by pivoting to internal knowledge for content generation

日本語の概要は準備中です。原文の説明を表示しています。

Debug Python script execution failures by capturing full tracebacks and verifying working directory

日本語の概要は準備中です。原文の説明を表示しています。

Graceful degradation workflow for ffmpeg encoding failures with progressive fallback strategies

日本語の概要は準備中です。原文の説明を表示しています。

Report tool failures transparently and attempt minimal viable output with disclaimers

日本語の概要は準備中です。原文の説明を表示しています。

Identify and classify agent failures occurring before execution starts

日本語の概要は準備中です。原文の説明を表示しています。

Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

日本語の概要は準備中です。原文の説明を表示しています。

Debug Python code execution failures by capturing partial traces, isolating failing functions, and incrementally verifying outputs

日本語の概要は準備中です。原文の説明を表示しています。

Handle code execution failures with fallback strategies and anchored workspace paths

日本語の概要は準備中です。原文の説明を表示しています。

Validates security patches with reproducible baseline-versus-patched evidence, including original exploits, root-cause variants, behavior preservation, regressions, and newly introduced security failures. Use after a patch exists and before accepting, merging, or reporting it as fixed; also use when an AI-generated patch, remediation commit, pull request, or proposed upstream fix needs adversarial post-patch validation across any language.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an OpenAI API request fails and Codex needs to classify the likely cause, explain the next step, and route to the right follow-up. Covers common runtime failures such as blocked outbound network access, invalid credentials, exhausted API quota or credits, rate limits, and model, project, or organization access issues; delegate key provisioning to openai-platform-api-key and current documentation lookups to openai-docs.

日本語の概要は準備中です。原文の説明を表示しています。

**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

日本語の概要は準備中です。原文の説明を表示しています。

Build, run, and debug macOS apps with shell-first Xcode and Swift workflows. Use when launching apps or diagnosing build, startup, or runtime failures.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect macOS signing, entitlements, and Gatekeeper issues. Use when diagnosing code signing, sandbox, hardened runtime, or trust failures.

日本語の概要は準備中です。原文の説明を表示しています。

Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare macOS packaging and notarization workflows. Use when archiving apps, validating bundles, or explaining distribution-only failures.

日本語の概要は準備中です。原文の説明を表示しています。

Evidence-first pull request judge that reviews a PR and posts one consolidated GitHub review with inline comments via the gh CLI. Runs the repo's own deterministic checks first, researches current official docs before any claim about external libraries or APIs, then reviews correctness, security, structural quality (code judo, spaghetti growth, file-size limits), and AI slop including useless code comments. Every finding must carry evidence, every comment passes a deterministic noise gate before posting, and the verdict (APPROVE, COMMENT, REQUEST_CHANGES) is weighed by findings. Use when asked to review a PR, judge this PR, review this branch or diff before merge, run the-judge, "revise esse PR", "faca o code review", or "julgue esse PR". Do NOT use for reviewing prose or documents, fixing CI failures, resolving merge conflicts, writing the fix itself, or responding to review comments (use gh-address-comments).

日本語の概要は準備中です。原文の説明を表示しています。

Monitor Nx Cloud CI pipeline status and handle self-healing fixes automatically. Use when user says "watch CI", "monitor pipeline", "check CI status", "fix CI failures", or "self-heal CI". Requires Nx Cloud connection. Do NOT use for local task execution (use nx-run-tasks) or general CI debugging outside Nx Cloud.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate Stripe payment failures and unexpected outcomes from exact object IDs, lifecycle state, events, amounts, currency, refunds, and dispute evidence.

日本語の概要は準備中です。原文の説明を表示しています。

**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

日本語の概要は準備中です。原文の説明を表示しています。