Scenario guide场景指南
Incident Debugging
Diagnose root cause before applying fixes.
The problem · 要解决的问题
Messy production bugs need evidence, hypotheses, and verification before code changes make the situation harder to reason about.
Recommended skills推荐 skill
4 picks · Best pick first, ranked by fit★ best fit · 首选
Incident Investigate
by Evan Hsu
Best fit when the team needs root-cause discipline before touching code.
- Evidence-first workflow
- Hypothesis tracking
- Verification before fix claims
GStack Investigate
by Garry Tan
Strong alternative for structured debugging with a heavier local investigation loop.
- Root-cause-first remediation
- Pattern analysis
- Regression-test encouragement
Canary Watch
by Joel Martinez
Useful for confirming whether a suspected deploy regression is visible in production.
- Live route sampling
- Post-deploy evidence
- Console error checks
Test Bench
by Anya Raghavan
Good after root cause is known and the missing regression test needs to be defined.
- Regression coverage
- CI focus