Squashed 'docs/standards/playbook/' changes from e504a68..b529012

b529012  test(tests): avoid hardcoded missing path
07583c8 🐛 fix(tests): make doc link check awk-portable
6244aa3 🔧 chore(ci): relax gitattributes check
31dd0c5 🐛 fix(scripts): require existing project root
15d4d63 🔧 chore(ci): install python3-pip
90c6313 🔧 chore(ci): run tests in a single job
d84eff0 🔧 chore(ci): make actions base url configurable
395598d 🔧 chore(ci): fix yaml step names
4ae2733  feat(sync_standards): auto-detect existing languages
e97fb00  feat(sync_standards): default gitattributes to append
da0ef2b  test: add automated tests and ci workflow
99bef30 🎨 style(markdown): format all markdown files with prettier
7e96bc8 ♻️ refactor(tsl): split function.md into 44 modular files
0d6b2a0 📝 docs(readme): add quick decision table and TL;DR for distribution methods
3b2188f 🎨 style(markdown): format markdown files with prettier
41fc43b 📝 docs(tsl): document {Unit.}Type source annotation
3dceaf7 📝 docs(tsl): clarify tsf-only top-level rules and type annotations
3a63829 📝 docs(skills): add create-plan skill
f02a707 🐛 fix(scripts): escape markdown backticks in vendor_playbook
064aa92 🐛 fix(scripts): correct bat scripts
4881feb 🔧 chore(gitattributes): enforce crlf for bat files
1fa3e2a 🐛 fix(scripts): escape parentheses in sync_standards output
3958cad 📝 docs(vendor_playbook): mention ci templates
9d059cf  feat(templates): add gitea ci example
a52bb24 📝 docs(codex_skills): normalize markdown formatting
cc8ad4c 📝 docs(skills): slim commit-message
2a98e15 🐛 fix(skills): quote YAML descriptions
8f78d22 🐛 fix(sync_standards): generate minimal AGENTS.md
5547665  feat(skills): add commit-message suggestion skill
3fe8bd7 🔧 chore(sync_standards): create AGENTS.md on sync
283d311  feat(playbook): add syntax book and codex skills tooling
5b97ed5 📝 docs(tsl): clarify syntax references
27e0700  feat(skills): add pdf/docx/pptx/xlsx wrapper workflows
5551363  feat(skills): add debugging and bulk refactor workflows
1d4f548  feat(skills): add built-in workflow skills
c0895dd 📝 docs(skills): add anthropics document-skills integration
cf9f80d 🔧 chore(playbook): add Claude Code skills guide and align python templates

git-subtree-dir: docs/standards/playbook
git-subtree-split: b529012c59c5d67c3073884d7b617763647417fd
This commit is contained in:
csh
2026-01-08 15:56:36 +08:00
parent eada742d75
commit ac794a6a70
113 changed files with 254751 additions and 176 deletions
@@ -0,0 +1,52 @@
---
name: systematic-debugging
description:
"Systematic debugging for bugs, failing tests, regressions (TSL/C++/Python).
Triggers: debug, failing test, regression, crash, 复现, 定位, 排查, 调试."
---
# Systematic Debugging(系统化调试)
## When to Use
- Bugs, crashes, failing/flaky tests, regressions
- “It doesnt work” reports with unclear reproduction
## Inputsrequired
- Expected vs actual behavior
- Repro command/steps (or best-known approximation)
- Logs/traces/screenshots/error output
- Environment details (OS, versions, configs)
## Proceduredefault
1. **Reproduce**
- Make the failure deterministic if possible
- Minimize repro steps (smallest input/command)
2. **Localize**
- Identify failing component and boundary conditions
- Add temporary logging/assertions if needed (then remove)
3. **Hypothesize & Test**
- Form a small number of hypotheses
- Design quick experiments to falsify each hypothesis
4. **Fix & Verify**
- Fix the root cause (not just symptoms)
- Add/update tests; rerun the minimal relevant suite
## Output Contractstable
- Repro: exact steps/command
- Diagnosis: root cause + evidence
- Fix: what changed + why it works
- Verification: commands + outputs/exit codes
- Follow-ups: hardening or cleanup tasks
## Guardrails
- Avoid changing multiple variables at once
- Prefer instrumentation and evidence over guessing
- Keep fixes minimal and scoped