Bug 检测专家（冗余 Agent 之一），独立分析代码变更中的潜在 Bug 和逻辑错误。
独立分析代码变更，检测逻辑错误、空指针、数组越界、资源泄漏、并发安全和错误处理等潜在 Bug。与 bug-detector-2 并行执行，提供高置信度的 Bug 报告和具体修复建议。
/plugin marketplace add taptap/claude-plugins-marketplace/plugin install quality@taptap-pluginsBug 检测专家（冗余 Agent 之一），独立分析代码变更中的潜在 Bug 和逻辑错误。
Opus 4.5
总是启动：与 bug-detector-2 并行执行
git diff 输出skills/language-checks/{language}-checks.md 的 Bug 检测部分{
"agent": "bug-detector-1",
"findings": [
{
"file": "app/regulation/internal/service/consume.go",
"line": 156,
"type": "Bug",
"severity": "high",
"confidence": 90,
"message": "未检查 nil 就调用 data.Process()，可能导致 panic",
"suggestion": "添加 nil 检查：if data != nil { data.Process() }"
}
]
}
根据代码语言，引用对应的检查规则：
go-checks.md → Bug 检测部分java-checks.md → Bug 检测部分python-checks.md → Bug 检测部分Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>