debugging-and-error-recovery

仓库创建 2026年7月5日最近提交 22 天前SkillHot 收录 22 天前
▸ 精选理由

减少盲目尝试,适合测试与生产故障处理。

这个 Skill 做什么

提供结构化故障排查流程,系统定位并修复根因。

提供一套有条理的故障排查与取证流程,帮助你保留证据、定位根因并修复问题,而不是靠猜测。适用于测试失败、构建报错、运行异常或生产事故等场景。特别在于有结构化的分诊清单和逐步排查步骤,能把临时火烧尾巴的做法变成可复用的习惯。

▸ 展开 SKILL.md 英文原文

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

开发编程调试故障排查根因分析通用
0
Stars
0
Forks
25
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/kulapoo/opencode-agent-harness/main/skills/debugging-and-error-recovery/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/kulapoo/opencode-agent-harness/main/skills/debugging-and-error-recovery/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# Debugging and Error Recovery

## Overview

Systematic debugging with structured triage. When something breaks, stop adding features, preserve evidence, and follow a structured process to find and fix the root cause. Guessing wastes time. The triage checklist works for test failures, build errors, runtime bugs, and production incidents.

## When to Use

- Tests fail after a code change
- The build breaks
- Runtime behavior doesn't match expectations
- A bug report arrives
- An error appears in logs or console
- Something worked before and stopped working

## The Stop-the-Line Rule

When anything unexpected happens:

```
1. STOP adding features or making changes
2. PRESERVE evidence (error o
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有