系統化除錯

來源狀態

尚未確認

搜尋索引仍可見原始內容，但直接來源讀取失敗；尚未確認搬遷、相容性或授權。

原始名稱: debug

原始作者: jscott3201

這是第三方 Community Skill；2lus 收錄不代表已完整安全審計或保證安全。

資源類型

Skill

與類似 Skill 有什麼不同？

• 單元測試設計 Agent

  Code Testing Agent 著重測試案例與驗證流程；Systematic Debugging 先收斂故障原因，再決定需要的驗證。

• 可觀測性

  Observability 建立 logs、metrics 與 traces 以提供證據；Systematic Debugging 使用可得證據調查特定故障。

來源描述的能力

這些是來源描述的可能操作，不代表 2lus 已授予權限或已測試。

尚未列出能力，請審查原始來源。

這個 Skill 是什麼？

先確認錯誤如何發生，再用證據淘汰假設並規劃回歸驗證，避免反覆猜測修法；原始 debug 來源目前待重新確認。

可以做什麼？何時適合使用？

• 同一個 bug 修過仍然出現。
• runtime error 沒有明確起點。
• 修改一個模組導致另一處退化。

如何使用

1. 收集去識別化錯誤、版本差異與最小重現條件。
2. 列出可證偽的假設與隔離方式，優先唯讀檢查。
3. 確認根因後提出最小修補與回歸計畫，動態重現需先取得授權。

使用前你需要準備

• 預期與實際行為
• 去識別化錯誤紀錄和相關程式

你可以替換：

[test framework]、[failure]

環境與相依需求

• 問題紀錄、相關程式與版本歷史；來源目前無法可靠存取，不提供安裝指令。

使用範例與 Prompt

以下是 2lus 撰寫的示範需求；請替換為你有權處理的檔案與專案，不代表已執行或保證結果。

入門

這個 bug 已修兩次仍出現，先從日誌整理重現條件與三個可驗證假設，不修改程式。

實務

比較最後正常與首個異常版本，提出隔離 callback 競態的計畫；列出每個假設所需的反證。

進階

為跨模組回歸設計 git bisect 和最小重現方案，先說明工作樹保護、動態執行授權與 regression case，不切換分支。

實用提醒

• 保留已排除假設及其證據，避免下一輪重新猜測。

限制與注意事項

• Git bisect 會切換版本；本指南不代表已確認原始 Skill 的現行相容性或授權。

安全注意事項

• 不要在有未提交修改的工作樹直接 bisect；不要對正式資料重現破壞性錯誤。

使用與設定

此條目不提供已確認的通用安裝指令；請依官方文件與 Agent 版本操作。

支援平台

未確認特定 Agent 相容性

來源與授權

來源查核日期（非安全認證）: 2026-09-29

請參考原始來源授權條款

相關 Skills

• 單元測試設計 Agent
• 一手來源技術研究

Source status

Unconfirmed

The original content remains indexed, but direct retrieval failed. Relocation, compatibility and licensing remain unconfirmed.

Original name: debug

Original author: jscott3201

This is a third-party community skill. Inclusion by 2lus is not a complete security audit or safety guarantee.

Resource type

Skill

How is this different from similar skills?

• Code Testing Agent

  Code Testing Agent focuses on test cases and verification workflow; Systematic Debugging narrows failure causes before selecting checks.

• Observability

  Observability instruments logs, metrics and traces; Systematic Debugging uses available evidence to investigate a specific failure.

Documented capabilities

These are operations described upstream, not permissions granted or tested by 2lus.

Capabilities not declared here; review the original source.

What is this skill?

Establish how a failure happens, eliminate hypotheses with evidence and plan regression checks instead of guessing successive fixes. The original debug source still needs confirmation.

Use cases and when to use it

• A bug returns after multiple fixes.
• A runtime error has no clear origin.
• A change in one module breaks another.

How to use it

1. Collect sanitized errors, version differences and minimal reproduction conditions.
2. State falsifiable hypotheses and isolation methods, starting with read-only inspection.
3. Propose a minimal fix and regression plan after identifying the cause; authorize dynamic reproduction separately.

What you need

• Expected and actual behavior
• Redacted errors and relevant code

You can replace:

[test framework], [failure]

Environment and dependencies

• Issue evidence, relevant code and version history; the source is not reliably accessible, so no installer is provided.

Usage and prompt examples

These example requests were written by 2lus. Substitute files and projects you may use; examples are not executed results or guarantees.

Beginner

This bug returned after two fixes. Extract reproduction conditions and three testable hypotheses from the logs without editing code.

Practical

Compare the last working and first failing versions. Plan isolation of a callback race and specify evidence that would disprove each hypothesis.

Advanced

Design bisect and minimal reproduction for a cross-module regression. Explain worktree protection, execution approval and regression cases; do not switch revisions.

Tips

• Retain rejected hypotheses with evidence to avoid restarting the same guesses.

Limitations

• Git bisect changes revisions; this guide does not establish current upstream compatibility or licensing.

Security notes

• Do not bisect a dirty worktree or reproduce destructive failures on production data.

Usage and setup

No verified universal installation command is provided for this entry. Follow the official documentation for your agent version.

Supported agents

Specific agent compatibility unknown

Sources and license

Source check date (not a safety certification): 2026-09-29

Refer to the original source license terms

Related skills

• Code Testing Agent
• Primary Source Research