← Back to Skills Marketplace
160
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install bug-reflection
Description
Bug修复流程规范：包含反省、检查模块逻辑语法、对比官方文档、性能检查，以及修复后写Fix Report。触发条件：用户反馈有bug时。
README (SKILL.md)
Bug Reflection & Fix Report
这个 Skill 用于管理 Bug 修复的完整流程，包括问题分析、检查验证、用户沟通和经验沉淀。
触发条件
当用户反馈有 Bug 时，必须立即触发此 Skill。
一、问题分析阶段
1.1 收集 Bug 信息
- 详细记录 Bug 的表现形式
- 了解触发 Bug 的操作步骤
- 记录错误日志、截图等相关信息
1.2 推断问题模块
永远不要直接打补丁。必须根据 Bug 表现推断可能产生问题的模块：
- 分析错误信息中的关键提示
- 定位相关代码模块
- 检查模块之间的调用关系
二、检查验证阶段
2.1 对比官方文档
检查模块的逻辑语法是否正确：
- 查阅官方文档说明
- 对比实际代码实现与文档规范
- 检查 API 使用方式、参数类型、返回值等
2.2 性能检查
- 检查代码是否存在性能问题
- 分析时间复杂度和空间复杂度
- 检查是否存在内存泄漏、死循环等问题
2.3 向用户确认
如果检查后认为没有问题，询问用户是否需要打补丁时，必须：
- 告知用户已检查的具体模块
- 说明检查的依据（官方文档、代码逻辑等）
- 解释为什么当前实现是合理的
- 提供替代方案或建议（如果用户仍希望修改）
三、Fix Report 书写规范
3.1 记录内容
修复完 Bug 后，必须将以下内容写入 Fix Report：
- Bug 描述：问题的具体表现
- 问题根因：导致 Bug 的根本原因
- 尝试过的方案：
- 成功的尝试
- 失败的尝试（以及失败原因）
- 最终解决方案：采用的修复方式
- 检查清单：
- 对比了哪些官方文档
- 检查了哪些模块
- 性能检查结果
- 经验教训：从这个 Bug 中学到什么
3.2 报告格式示例
# Fix Report - [Bug名称]
## Bug 描述
[详细描述问题表现]
## 问题根因
[分析导致问题的根本原因]
## 尝试记录
### 尝试 1：[方案名称]
- 结果：成功/失败
- 原因：[成功原因/失败原因]
### 尝试 2：[方案名称]
- 结果：成功/失败
- 原因：[成功原因/失败原因]
## 最终方案
[采用的修复方式]
## 检查清单
- [ ] 已对比官方文档：XXX
- [ ] 已检查模块：XXX
- [ ] 性能检查：XXX
## 经验教训
[从这个 Bug 学到的经验]
四、经验复用
- 在修复新的 Bug 时，查阅历史 Fix Report
- 确保犯过的错误不再重复
- 将常见的排查方法整理成知识库
- 定期回顾 Fix Report，优化排查流程
关键原则
- 不盲目打补丁：先分析问题，找到根因
- 彻底检查：对比官方文档，检查逻辑语法和性能
- 透明沟通：向用户清晰说明检查过程和结果
- 经验沉淀：所有尝试都记录到 Fix Report
Usage Guidance
This skill is coherent and appears safe: it only describes a debugging process and asks for no secrets or installs. Before enabling, confirm how the agent will obtain logs and code (you may need to upload or grant repository access), avoid sharing sensitive secrets in Fix Reports, and consider trying it in a sandbox or with redacted data to verify behavior. If you do not want automatic invocation on every bug report, keep it user-invocable (it is not set to always:true).
Capability Analysis
Type: OpenClaw Skill
Name: bug-reflection
Version: 1.0.0
The skill bundle defines a structured procedural workflow for bug analysis, documentation, and reporting. The instructions in SKILL.md are focused on software engineering best practices such as root cause analysis and performance checking, and contain no malicious commands, data exfiltration logic, or harmful prompt injection attempts.
Capability Assessment
Purpose & Capability
The name and description (bug reflection / fix report workflow) match the SKILL.md instructions: collect bug info, analyze modules, check docs, run performance checks, and write a Fix Report. No unrelated binaries, env vars, or installs are requested.
Instruction Scope
The instructions are focused on troubleshooting and reporting steps. They recommend collecting logs, screenshots, inspecting code modules, and comparing with official docs — all reasonable for a debugging workflow. Note: the skill states it must be triggered immediately on user bug reports, so using it may involve accessing project logs/code that the user must explicitly provide or permit.
Install Mechanism
No install spec and no code files are present (instruction-only). This minimizes disk writes and third‑party downloads.
Credentials
The skill requests no environment variables, credentials, or config paths. Any access to logs or code would come from the agent's normal access to conversation or user-supplied files, which is proportionate to the stated purpose.
Persistence & Privilege
always:false and no self-install behavior. The skill does not request persistent presence or elevated privileges beyond normal agent invocation.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install bug-reflection - After installation, invoke the skill by name or use
/bug-reflection - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
bug-reflection 1.0.0 — 首个版本上线，规范完整 Bug 修复流程
- 明确用户反馈 Bug 时的触发条件及全流程要求
- 细化问题分析、模块定位、逻辑语法/官方文档对比、性能检查等环节
- 定义用户沟通注意事项，避免直接打补丁，确保透明说明
- 提供详细 Fix Report 模板，强调经验总结与复用
- 强调流程中的规范与复盘，促进知识积累
Metadata
Frequently Asked Questions
What is bug reflection for debugging?
Bug修复流程规范：包含反省、检查模块逻辑语法、对比官方文档、性能检查，以及修复后写Fix Report。触发条件：用户反馈有bug时。 It is an AI Agent Skill for Claude Code / OpenClaw, with 160 downloads so far.
How do I install bug reflection for debugging?
Run "/install bug-reflection" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is bug reflection for debugging free?
Yes, bug reflection for debugging is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does bug reflection for debugging support?
bug reflection for debugging is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created bug reflection for debugging?
It is built and maintained by 妹妹睡着了 (@miyahui); the current version is v1.0.0.
More Skills