团队规范
adr-process-debugging
更新于 2026-08-09
ADR Process · 调试规则
Debugging rules for ADR Process: minimal reproduction, one hypothesis per step and a regression test before the fix.
- 技术栈
- ADR Process
- 主题
- 调试
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Reproduce with the smallest input that still fails
- ✓ Bisect by evidence: logs, traces, and a single hypothesis per step
- ✓ Write the regression test before fixing the cause
✕ 常见反模式
- ✕ Changing several things at once to "see if it helps"
- ✕ Closing an issue on a flaky repro without a test
- ✕ Silencing the symptom instead of removing the cause
◎ 交付前验证
- ◎ Typecheck (`tsc --noEmit` or equivalent) passes with zero errors
- ◎ Lint passes and no rule was disabled inline
- ◎ Node/browser runtime compatibility checked against the project engines field
同分类条目
17 篇团队规范
Git Conventions 工程规则
Commit rules: conventional prefixes, scoped messages and revertible history
团队规范
Branching 工程规则
Branching rules: short-lived branches and a single integration source of truth
团队规范
Monorepo 工程规则
Monorepo rules: workspace boundaries, affected builds and lockfile discipline
团队规范
Dependency Upgrades 工程规则
Upgrade rules: pinned versions, changelog review and staged rollout
团队规范
ADR Process 工程规则
ADR rules: one decision per record with explicit consequences
团队规范
Local Dev Environment 工程规则
Dev environment rules: one command bootstrap and reproducible toolchains