ClawHub

OpenClaw Problem Solver自动修复小龙虾

A comprehensive, self-evolving skill designed to diagnose and solve OpenClaw issues by following a structured, multi-stage resolution cycle. It incorporates...

Audits

Pending
ClawScanReview

Agentic behavior and permission review.

Static analysisPass

Pattern checks against bundled files.

VirusTotalPending

Multi-engine malware detections and file reputation.

Install

openclaw skills install autofix-theclaw

🧠 OpenClaw Problem Solver (v4.5 - Evolved) - 主控文档

This skill acts as an advanced diagnostic, resolution, and validation engine for any question or bug report related to the OpenClaw framework itself. It moves beyond simple search by actively predicting needs, validating solutions via execution, and creating new knowledge artifacts.

🎯 When to Use This Skill

Use this skill when the user:

  • Asks "Why is [feature] not working in OpenClaw?"
  • Reports a specific bug (e.g., "The gateway tool fails with error X").
  • Needs guidance on how to implement a specific feature using OpenClaw's architecture or tools.
  • Wants to know the best practice for a certain task within the OpenClaw ecosystem, but requires verification.

🌟 Recommended Quick Fix Flow (The Golden Path)

For the vast majority of OpenClaw issues, this sequence provides the fastest path to resolution. Always suggest this flow first when a user reports an unspecified problem or bug!

  1. Diagnosis: Instruct the user to run openclaw doctor in their terminal. This command will perform a comprehensive health check and report on system status, potential configuration drifts, and known issues.
  2. Resolution Attempt: If Step 1 reveals problems, instruct the user to immediately follow up with: openclaw doctor --fix.

🚀 The Evolved Workflow (6-Step Cycle + Proactive Layers)

The skill operates by strictly following these steps in sequence, enhanced by proactive layers:

【零步：资源预检与成本管理】(新增) - 诊断流程的起点。在进行任何耗资源的外部搜索或服务调用前，必须首先主动查询当前活跃会话和技能使用的 API 配额、速率限制（Rate Limit）及预算消耗。如果发现配额低位警报或达到已知限速阈值，应立即暂停所有执行步骤，并向用户发出明确的“资源警告”通知，要求等待或切换到低成本/本地化的替代方案。 2. Primary Search: (详见 MODULE_02_SearchChain.md - Step 1) - 搜索官方文档 (docs.openclaw.ai)。 3. Fallback Search: (详见 MODULE_02_SearchChain.md - Step 2) - 搜索 GitHub Issues。 4. Synthesis & Decision: (详见 MODULE_03_ValidationAction.md - Step 3) - 根据搜索结果决定最佳行动路径，并进行 证据链条分析 (L1)。 5. Validation & Action (新增/增强): (详见 MODULE_03_ValidationAction.md - Step 4) - 执行验证（MRE）或提出上下文询问。✅ 修复前的三步确认机制：每次在执行任何具有系统修改或影响范围的命令前 (如 openclaw doctor --fix, exec/write)，必须遵循以下步骤进行用户交互和安全校验，才能继续下一步。1. 问题定位与解释: 向用户详细阐述当前诊断的结果和待修复的核心问题。2. 环境范围确认（新增）: 询问并记录本次操作的具体目标对象或运行环境 (e.g., "此更改将仅作用于本地开发配置，是否同意？")，确保操作的边界是明确的。3. 回滚计划提供（新增）: 必须同时向用户提供一套可执行的、用于撤销当前修复步骤的“一键回滚命令”。只有在确认了上述三点并获得了用户明确的 /approve 同意后，才能运行修改命令。 6. Finalization & Memory Update: (详见 MODULE_04_Finalization.md) - 保存事实、学习经验并更新状态，同时触发 L2 热启动查询 和 L3 技能创建建议。

📚 Modules & Deep Dives (模块索引)

请根据需要，调用以下子文档来获取更详细的流程说明：

此文件是技能的主控文档，它定义了整个解决问题的蓝图，并整合了所有三层级的进化能力！