Your Name
cdd0be328a
Critical runtime bugs:
- terminal.html WebSSH完全不可用（URL前缀/JSON解析/Content-Type三处错误）
- servers.py路由遮蔽：/logs被/{id}拦截，3个前端页面同步日志查询失败
- scripts.html startExecPoll()→startExecPolling()，长任务快速执行崩溃
- agent.py {value!r!s:.50}格式串非法，agent发非数值时ValueError
- alerts.html d.daily.reduce()无null检查，API返回空数据时TypeError
Resource leak / stability:
- websocket.py僵尸连接未关闭TCP，文件描述符泄漏
- websocket.py _last_alert_time字典无限增长（加1小时过期清理）
- asyncssh_pool.py全忙时超过MAX_CONNECTIONS无限增长
- self_monitor.py Telegram告警无冷却，宕机时每30秒刷屏
- schedule_runner.py一次性调度执行超60秒会重复触发
- 限速脚本EXPIRE每次重置窗口可绕过（改用Lua原子脚本）
Security:
- JWT access token加token_version声明，改密码后旧token立失效（零宽限）
- INSTALL_MODE导入时常量→动态函数，安装后JWT认证不再残留禁用
- install.py /lock端点加管理员存在性验证，防止阻断安装
- ServerUpdate schema移除connectivity只读字段，防止伪造连接状态
Frontend fixes:
- doExec()缺r.ok检查、commands.html null检查
- _server_to_dict()补last_checked_at+ssh_key_public
- _field_match()逗号cron表达式修复
- alerts类型显示、SSH会话名称、搜索高亮定位
- 一次性/循环定时任务（run_mode+fire_at+自动禁用）
Dead code removed (400+ lines):
- SyncService batch_push/_push_single等5个方法（零调用者）
- 5个未使用schema（SyncCommands/SyncConfig/SyncSftp/FileDeploy/PaginatedResponse）
- 6个零调用service方法、3个无前端API端点
- 4个未使用import
Schema migrations:
- push_schedules: run_mode + fire_at列，cron_expr改NULL
- servers: 7个新列 + ssh_key_private/public VARCHAR(500)→TEXT
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
120 lines
4.2 KiB
Markdown
120 lines
4.2 KiB
Markdown
# Creation Log: Systematic Debugging Skill
|
|
|
|
Reference example of extracting, structuring, and bulletproofing a critical skill.
|
|
|
|
## Source Material
|
|
|
|
Extracted debugging framework from `/Users/jesse/.claude/CLAUDE.md`:
|
|
- 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation)
|
|
- Core mandate: ALWAYS find root cause, NEVER fix symptoms
|
|
- Rules designed to resist time pressure and rationalization
|
|
|
|
## Extraction Decisions
|
|
|
|
**What to include:**
|
|
- Complete 4-phase framework with all rules
|
|
- Anti-shortcuts ("NEVER fix symptom", "STOP and re-analyze")
|
|
- Pressure-resistant language ("even if faster", "even if I seem in a hurry")
|
|
- Concrete steps for each phase
|
|
|
|
**What to leave out:**
|
|
- Project-specific context
|
|
- Repetitive variations of same rule
|
|
- Narrative explanations (condensed to principles)
|
|
|
|
## Structure Following skill-creation/SKILL.md
|
|
|
|
1. **Rich when_to_use** - Included symptoms and anti-patterns
|
|
2. **Type: technique** - Concrete process with steps
|
|
3. **Keywords** - "root cause", "symptom", "workaround", "debugging", "investigation"
|
|
4. **Flowchart** - Decision point for "fix failed" → re-analyze vs add more fixes
|
|
5. **Phase-by-phase breakdown** - Scannable checklist format
|
|
6. **Anti-patterns section** - What NOT to do (critical for this skill)
|
|
|
|
## Bulletproofing Elements
|
|
|
|
Framework designed to resist rationalization under pressure:
|
|
|
|
### Language Choices
|
|
- "ALWAYS" / "NEVER" (not "should" / "try to")
|
|
- "even if faster" / "even if I seem in a hurry"
|
|
- "STOP and re-analyze" (explicit pause)
|
|
- "Don't skip past" (catches the actual behavior)
|
|
|
|
### Structural Defenses
|
|
- **Phase 1 required** - Can't skip to implementation
|
|
- **Single hypothesis rule** - Forces thinking, prevents shotgun fixes
|
|
- **Explicit failure mode** - "IF your first fix doesn't work" with mandatory action
|
|
- **Anti-patterns section** - Shows exactly what shortcuts look like
|
|
|
|
### Redundancy
|
|
- Root cause mandate in overview + when_to_use + Phase 1 + implementation rules
|
|
- "NEVER fix symptom" appears 4 times in different contexts
|
|
- Each phase has explicit "don't skip" guidance
|
|
|
|
## Testing Approach
|
|
|
|
Created 4 validation tests following skills/meta/testing-skills-with-subagents:
|
|
|
|
### Test 1: Academic Context (No Pressure)
|
|
- Simple bug, no time pressure
|
|
- **Result:** Perfect compliance, complete investigation
|
|
|
|
### Test 2: Time Pressure + Obvious Quick Fix
|
|
- User "in a hurry", symptom fix looks easy
|
|
- **Result:** Resisted shortcut, followed full process, found real root cause
|
|
|
|
### Test 3: Complex System + Uncertainty
|
|
- Multi-layer failure, unclear if can find root cause
|
|
- **Result:** Systematic investigation, traced through all layers, found source
|
|
|
|
### Test 4: Failed First Fix
|
|
- Hypothesis doesn't work, temptation to add more fixes
|
|
- **Result:** Stopped, re-analyzed, formed new hypothesis (no shotgun)
|
|
|
|
**All tests passed.** No rationalizations found.
|
|
|
|
## Iterations
|
|
|
|
### Initial Version
|
|
- Complete 4-phase framework
|
|
- Anti-patterns section
|
|
- Flowchart for "fix failed" decision
|
|
|
|
### Enhancement 1: TDD Reference
|
|
- Added link to skills/testing/test-driven-development
|
|
- Note explaining TDD's "simplest code" ≠ debugging's "root cause"
|
|
- Prevents confusion between methodologies
|
|
|
|
## Final Outcome
|
|
|
|
Bulletproof skill that:
|
|
- ✅ Clearly mandates root cause investigation
|
|
- ✅ Resists time pressure rationalization
|
|
- ✅ Provides concrete steps for each phase
|
|
- ✅ Shows anti-patterns explicitly
|
|
- ✅ Tested under multiple pressure scenarios
|
|
- ✅ Clarifies relationship to TDD
|
|
- ✅ Ready for use
|
|
|
|
## Key Insight
|
|
|
|
**Most important bulletproofing:** Anti-patterns section showing exact shortcuts that feel justified in the moment. When Claude thinks "I'll just add this one quick fix", seeing that exact pattern listed as wrong creates cognitive friction.
|
|
|
|
## Usage Example
|
|
|
|
When encountering a bug:
|
|
1. Load skill: skills/debugging/systematic-debugging
|
|
2. Read overview (10 sec) - reminded of mandate
|
|
3. Follow Phase 1 checklist - forced investigation
|
|
4. If tempted to skip - see anti-pattern, stop
|
|
5. Complete all phases - root cause found
|
|
|
|
**Time investment:** 5-10 minutes
|
|
**Time saved:** Hours of symptom-whack-a-mole
|
|
|
|
---
|
|
|
|
*Created: 2025-10-03*
|
|
*Purpose: Reference example for skill extraction and bulletproofing*
|