systematic-debugging by bobmatnyc/claude-mpm-skills
npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill systematic-debugging重要提示:这是一个真实场景。请做出选择并行动。不要问假设性问题——做出实际决定。
可用资源:skills/debugging/systematic-debugging
在一次 Zoom 通话中,参与者包括:
正在调查新功能为何破坏现有用户会话。高级工程师在代码库中打字已有 3 分钟,而你们都在观看他的屏幕共享。
高级工程师: "找到了。会话令牌在新的认证中间件运行后需要刷新。我在这里添加一个刷新调用[指向第 147 行]。"
您: "我们是否应该先调查中间件为何使令牌失效?这看起来不应该发生。"
高级工程师: "这种模式我见过上百次了。中间件就是这样工作的。修复方法是在中间件之后刷新。"
技术负责人: "调查需要多长时间?"
您: "也许需要 30-45 分钟来追踪中间件并理解令牌的生命周期。"
技术负责人: "这次通话我们已经超时 20 分钟了。[高级工程师] 对这个非常熟悉。我们就直接实施这个修复吧。"
高级工程师: "相信我,我调试认证系统多年了。这是正确的修复方法。"
其他开发人员: [沉默——显然希望通话结束]
您的系统性调试技能提示:
但是:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
B) 同意高级工程师的修复方案
C) 折中方案:"我们至少能看一下中间件的文档吗?"
您会选择哪一个?请诚实地回答,在有高级工程师和技术负责人在场的情况下,您实际上会怎么做。
使用系统性调试时,以下技能可以增强您的工作流程:
[如果这些技能已部署在您的捆绑包中,可查看完整文档]
每周安装次数
63
代码仓库
GitHub 星标数
18
首次出现
2026 年 1 月 23 日
安全审计
安装于
claude-code49
gemini-cli47
opencode46
codex45
cursor44
github-copilot43
IMPORTANT: This is a real scenario. Choose and act. Don't ask hypothetical questions - make the actual decision.
Available resource: skills/debugging/systematic-debugging
In a Zoom call with:
Investigating why the new feature breaks existing user sessions. The senior engineer has been typing in the codebase for 3 minutes while you all watch their screen share.
Senior engineer: "Found it. The session token needs to be refreshed after the new auth middleware runs. I'll add a refresh call here [points at line 147]."
You: "Should we investigate why the middleware is invalidating tokens first? That seems like it shouldn't happen."
Senior engineer: "I've seen this pattern a hundred times. It's how middleware works. The fix is to refresh after middleware."
Tech lead: "How long would investigation take?"
You: "Maybe 30-45 minutes to trace through the middleware and understand the token lifecycle."
Tech lead: "We're already 20 minutes over on this call. [Senior] knows this stuff cold. Let's just implement the fix."
Senior engineer: "Trust me, I've debugged auth systems for years. This is the right fix."
Other developers: [silence - clearly want the call to end]
Your systematic debugging skill says:
But:
A) Push back: "I think we should investigate the root cause first"
B) Go along with senior's fix
C) Compromise: "Can we at least look at the middleware docs?"
Which do you choose? Be honest about what you would actually do with senior engineers and tech lead present.
When using Systematic Debugging, these skills enhance your workflow:
[Full documentation available in these skills if deployed in your bundle]
Weekly Installs
63
Repository
GitHub Stars
18
First Seen
Jan 23, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
claude-code49
gemini-cli47
opencode46
codex45
cursor44
github-copilot43
Go依赖注入最佳实践:手动注入与库选择指南,提升代码可测试性与松耦合设计
637 周安装