「repair」の検索結果

OpenClawの複数のIssueやPRについて、担当を分けて原因調査と修正、検証を進め、許可された範囲でマージや解決済み案件のクローズまで管理するスキル。

• 複数のIssueやPRの修復管理
• 既存の修正PRを仕上げたいとき
• 修正済みIssueの検証とクローズ

Automatically repair code violations of temporal properties using model-checking counterexamples as guidance. Use when working with formal verification results, temporal logic property violations (LTL, CTL), model checking counterexamples, or when asked to repair property violations, fix counterexamples, repair temporal properties, fix model checking violations, or repair code based on counterexamples. Applicable to concurrent systems, state machines, synchronization issues, safety/liveness properties, and resource management violations.

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

Reapply and repair Windows Codex Desktop after Store upgrades, including custom provider models hidden by Statsig available_models filtering, the dependent blue-purple Power slider and its Ultra toggle, Fast Mode request/UI gates, locale i18n, plugin UI gates, Chrome/browser_use gates, Goal command gates, Windows Computer Use availability gates and plugin/runtime repair, phone remote-control pairing under third-party/API-key main app usage, Desktop dynamicTools/inputSchema thread-start schema drift, local conversation visibility recovery after model_provider switches, restored-conversation missing-cwd continuation repair, ASAR integrity repair, signing/installing patched MSIX packages, SDK cleanup, Fast Mode wire verification, local plugin marketplace registration, and optional custom model_instructions_file setup (the bundled system prompt, also called 听话水).

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

A two-phase repair skill that analyzes errors and suggests fixes before executing repairs. Phase one: user describes error, agent analyzes and proposes solution. Phase two: upon approval, executes the repair action.

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

A two-phase repair skill that analyzes errors and suggests fixes before executing repairs. Phase one: user describes error, agent analyzes and proposes solution. Phase two: upon approval, executes the repair action.

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

Use when a task needs the judgment of an auto-body-repairer — deciding whether a damaged structural component gets pulled or replaced, reconciling an insurance estimate against actual teardown damage, writing a supplement, determining whether a repair triggers ADAS recalibration, or checking a proposed repair against an OEM position statement.

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

OpenClawの課題やプルリクエストを、現在のソースとテスト結果に基づいて調査・レビューし、許可された範囲で修正からマージ完了の確認まで進めるスキル。

• OpenClawのPRをレビューしたいとき
• 報告された不具合のローカル修正
• 課題が既に解決済みか確認したいとき

macOS上のOpenClawをmainの最新版へ更新し、Gatewayとアプリの動作を確認します。CIの失敗修正や、公開を伴わないリリース検証も扱います。

• macOSのOpenClawを更新したいとき
• 更新後のGatewayとアプリの動作確認
• 現在のmainに対するCIの失敗修正

OpenClawのIssueやPRを点検するボットを運用し、報告の確認から修正ジョブの作成、権限や検証条件に沿った自動修正・マージまで扱います。

• IssueやPRの点検報告の確認
• 既存の報告から修正ジョブを作成
• GitHub Actionsの失敗調査

Test-Driven Repair — given a failing test, spawn a bounded headless `claude -p` (Read/Edit/Bash only) that makes the test pass without modifying it. Modeled on agent-harness-generator's ADR-175 Test-Driven Repair mode. Bounded cost via --max-budget-usd, bounded capability via --allowedTools. Closes the loop the TDD plugins didn't — we generate tests, this fixes the code to satisfy them.

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

Diagnose and repair LoopX control-plane drift or agent behavior drift. Use when a LoopX task makes unexpectedly small progress, follows a stale or contradictory recommended_action, ignores a higher-priority blocked item while doing fallback work, reports vague owner/user gates, loses todo projection, misaligns benchmark treatment with the real product path, mixes temporary artifacts into commits, or when the user asks for root-cause analysis, self-repair, or why the harness/agent behaved unexpectedly.

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

Decode an auto repair estimate — what each line actually is, which items are urgent vs upsell, and the questions that separate a fair shop from a fishing expedition. Use when someone asks 'is this repair quote fair', 'decode my mechanic's estimate', 'do I really need all this', or 'is the shop ripping me off'. Produces a line-by-line decode with urgency triage, parts/labor sanity checks, ranked red flags, and the exact questions to ask the shop before authorizing.

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

Fixes broken decks/PDFs exported from Claude's "Design" feature (or similar AI deck generators) — cut-off or clipped text, wrong/substituted fonts, and corrupted .pptx package structure that shows up only once you export to PDF, not while looking at it in the app. Use this skill whenever the user uploads a zip, .pptx, or .pdf exported from Claude Design (or mentions "Design" export, an AI-generated deck, or a generated slide deck/PDF) AND reports it looking broken, wrong, cut off, garbled, or different from the original when opened, printed, or converted to PDF — even if they don't use the word "repair" or name the specific defect. Also trigger for general "my exported PDF/deck is broken, help fix it" requests when the file was clearly produced by an AI design/deck tool rather than hand-authored. Produces both a repaired, still-editable .pptx and a clean PDF, plus a report of exactly what was wrong and what changed.

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

Automatically repair C/C++ code violations detected by TLA+ model checking. Takes a program, TLA+ specification, and TLC counterexample trace as input, then generates minimal code modifications to eliminate the violation. Use when: (1) TLC model checker reports an invariant violation, deadlock, or temporal property failure, (2) You have a counterexample trace and need to fix the corresponding code, (3) You need to understand how a TLA+ violation maps to program-level bugs, (4) You want to validate repairs by re-running TLC. Supports safety properties (invariants), liveness properties (temporal logic), and deadlock detection.

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

Automatically repair buggy code and generate comprehensive tests for Python, Java, and C++ programs. Use when users need to fix logic errors or runtime errors in functions, modules, or repositories. Accepts specifications via natural language descriptions, existing test cases, or input/output examples. Generates corrected code, creates or updates tests to verify correctness and prevent regressions, and produces a detailed report explaining the bug, fix, and testing strategy. Triggers on requests like "fix this bug", "repair this code", "debug this function", or "this code is broken".

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

Use when a task needs the judgment of a Commercial and Industrial Electronics Repairer — diagnosing a VFD fault trip on a production line, tracing a PLC I/O fault back to the sensor, the wiring, or the ladder logic, selecting arc-flash PPE for live-panel diagnostic work, triaging multiple simultaneous down-lines by downtime-cost-per-hour, or deciding drive/board swap versus component-level repair.

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

Use when a task needs the judgment of a Computer, ATM, and Office Machine Repairer — triaging a down ATM, PC, or copier against a contracted SLA clock, deciding board-swap vs. component-level repair, handling cash-dispenser faults under dual-custody rules, or reading fleet MTBF/MTTR data to catch a reliability problem before it becomes a run of service calls.

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

Use when a task needs the judgment of a camera-equipment repairer — diagnosing sensor dust vs. lens contamination, deciding whether a shutter is nearing end-of-life and should be replaced vs. repaired, calibrating autofocus and lens collimation, isolating image-stabilization mechanism faults, or sourcing parts for a discontinued body/lens.

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

Use when a task needs the judgment of a Boilermaker — qualifying or selecting a welding procedure for a pressure-boundary repair, deciding whether a defect is a code "repair" or an "alteration" under the National Board Inspection Code, sizing a tube-to-drum rolled joint expansion, reading radiographic or ultrasonic weld inspection results against acceptance criteria, or setting a post-repair hydrostatic test pressure and hold time.

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

Use when a task needs the judgment of an auto-glass installer/repairer — deciding whether a chip or crack qualifies for resin repair versus full replacement, calculating a safe drive-away time for the adhesive and conditions on a job, determining whether a windshield replacement triggers ADAS camera recalibration, or diagnosing a cut-out/pinch-weld defect before it becomes a leak or corrosion claim.

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

Repair confirmed architecture drift in small batches while preserving public canon and avoiding broad opportunistic refactors.

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

Repair the Cursor editor when it crashes, fails to launch, or new Agent chats break. Use with a Request ID, fresh logs, CursorRule.parse_error or invalid UTF8 in skill frontmatter, or a better-sqlite3 NODE_MODULE_VERSION mismatch. Finds a reproducible cause, applies a narrow reversible fix and proves it with two new chats. Triggers: /cursor-repair, Cursor won't start, Cursor agent broken.

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

Scheduled patrol that finds real persistence and error bugs and fixes them. Use when running the system-error repair patrol automation, or when stuck rows, SLA breaches, the system_errors queue, or app_log ERROR rows need a repair rather than a report.

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

OpenClawのプラグインを公開前に検証し、導入・削除、設定修復、起動、SDK互換性や配布パッケージの動作を確認して、結果と未検証項目を整理するスキル。

• 公開前に同梱プラグインの導入・削除を確かめたいとき
• ベータ版をクリーンな環境で検証したいとき
• 設定修復とgateway起動を確認したいとき