Skills when-debugging-code-use-debugging-assistant
📦

when-debugging-code-use-debugging-assistant

Content revision r1 High Risk ⚙️ External commands🔑 Env variables📁 Filesystem access

透過根本原因分析偵錯程式碼

當症狀、原因、修復與測試被分開處理時,偵錯可能會停滯。此技能會引導一套五階段工作流程,用於診斷、修復、驗證與預防迴歸。

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it ⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "when-debugging-code-use-debugging-assistant" from https://skillstore.io/skills/dnyoussef-when-debugging-code-use-debugging-assistant.md and its manifest at https://skillstore.io/api/skills/dnyoussef-when-debugging-code-use-debugging-assistant/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "when-debugging-code-use-debugging-assistant". 使用者在近期部署後看到登入錯誤。

Expected outcome:

  • 症狀摘要列出失敗路徑、觀察到的錯誤、受影響使用者與重現狀態。
  • 根本原因分析聚焦於近期驗證變更與缺少的使用者物件驗證。
  • 驗證計畫包含登入迴歸測試,以及缺少使用者資料的負面案例。

Using "when-debugging-code-use-debugging-assistant". 結帳測試在平行執行期間間歇性失敗。

Expected outcome:

  • 此工作流程會將時序症狀與資料損毀症狀分開。
  • 可能原因被描述為需要隔離的共享狀態或順序問題。
  • 預防步驟包含確定性的迴歸測試,以及給未來審查者的備註。

Using "when-debugging-code-use-debugging-assistant". 新增事件監聽器後出現記憶體洩漏。

Expected outcome:

  • 此報告將監聽器生命週期檢查識別為主要調查路徑。
  • 修復計畫強調清理行為與可衡量的記憶體驗證。
  • 迴歸預防會新增 teardown 檢查與監控備註。

Security Audit

High Risk
v9 • 7/5/2026 Open versioned report

Most static findings are false positives from Markdown examples, Graphviz labels, and /dev/null redirection. The executable shell workflow has real risks from eval on a project-configured test command and repeated npx execution of a mutable alpha package. No prompt injection attempt was found in the reviewed files.

7
Files scanned
3,391
Lines analyzed
8
Review items
0
False positives ignored

Confirmed security concerns (2)

High
Configurable Test Command Uses eval
The shell workflow loads testCommand from .debug-config.json into DEBUG_TEST_CMD and later runs eval on that value. A malicious or untrusted project configuration can execute arbitrary shell commands when validation runs.
The data flow is direct: jq reads testCommand from local config, assigns DEBUG_TEST_CMD, and eval executes it during validation.
High
Mutable npx Package Execution
The script repeatedly invokes npx claude-flow@alpha for hooks and memory operations. The alpha tag is mutable and may fetch and execute external npm package code at runtime.
The file shows repeated runtime npx calls to claude-flow@alpha, which is external package execution through a mutable npm dist tag.
Capability review items (8)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
Shell command substitution
export DEBUG_TEST_CMD=$(jq -r '.testCommand // "npm test"' "$config_file")
This reads .debug-config.json testCommand into DEBUG_TEST_CMD, which the script later executes with eval. A malicious or untrusted project config can control shell execution during validation.
Medium
Shell command substitution
symptoms=$(npx claude-flow@alpha memory retrieve \
This command substitution executes npx claude-flow@alpha during the workflow. The arguments are quoted, but running a mutable external npm package is a real external-command risk.
Medium
Shell command substitution
root_cause=$(npx claude-flow@alpha memory retrieve \
This command substitution executes npx claude-flow@alpha to retrieve workflow state. The command appears intentional, but mutable npx package execution remains a supply-chain risk.
Medium
Shell command substitution
local symptoms=$(npx claude-flow@alpha memory retrieve --key "debug/$issue_id/symptoms" 2>/dev/null
This status command executes npx claude-flow@alpha and captures its output. There is no obvious injection vector, but mutable external package execution is still a real risk.
Medium
Shell command substitution
local root_cause=$(npx claude-flow@alpha memory retrieve --key "debug/$issue_id/root-cause" 2>/dev/n
This status command executes npx claude-flow@alpha and captures its output. There is no obvious injection vector, but mutable external package execution is still a real risk.
Medium
Shell command substitution
local fix=$(npx claude-flow@alpha memory retrieve --key "debug/$issue_id/fix" 2>/dev/null || echo "P
This status command executes npx claude-flow@alpha and captures its output. There is no obvious injection vector, but mutable external package execution is still a real risk.
Medium
Shell command substitution
local validation=$(npx claude-flow@alpha memory retrieve --key "debug/$issue_id/validation" 2>/dev/n
This status command executes npx claude-flow@alpha and captures its output. There is no obvious injection vector, but mutable external package execution is still a real risk.
Medium
Shell command substitution
local prevention=$(npx claude-flow@alpha memory retrieve --key "debug/$issue_id/prevention" 2>/dev/n
This status command executes npx claude-flow@alpha and captures its output. There is no obvious injection vector, but mutable external package execution is still a real risk.

Risk Factors

⚙️ External commands (50)
🔑 Env variables (2)
📁 Filesystem access (19)
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/dnyoussef-when-debugging-code-use-debugging-assistant/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/dnyoussef-when-debugging-code-use-debugging-assistant/security.svg)](https://skillstore.io/skills/dnyoussef-when-debugging-code-use-debugging-assistant?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/dnyoussef-when-debugging-code-use-debugging-assistant?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dnyoussef-when-debugging-code-use-debugging-assistant/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/dnyoussef-when-debugging-code-use-debugging-assistant.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

DNYoussef. (2026). when-debugging-code-use-debugging-assistant security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dnyoussef-when-debugging-code-use-debugging-assistant/audits/9

BibTeX citation

@techreport{dnyoussef-dnyoussef-when-debugging-code-use-debugging-assistant-2026, author = {DNYoussef}, title = {when-debugging-code-use-debugging-assistant security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/dnyoussef-when-debugging-code-use-debugging-assistant/audits/9}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "when-debugging-code-use-debugging-assistant security audit report (audit version 9)" version: "unspecified" type: report authors: - name: "DNYoussef" date-released: "2026-07-05" url: "https://skillstore.io/skills/dnyoussef-when-debugging-code-use-debugging-assistant/audits/9" identifiers: - type: other value: "skillstore:dnyoussef-when-debugging-code-use-debugging-assistant:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
70
Community
91
Spec Compliance

What You Can Build

診斷生產環境迴歸

從症狀追蹤回報的失敗到根本原因,然後準備經測試的修復計畫。

將失敗轉化為迴歸測試

將失敗情境轉換為重現步驟、驗證測試與預防備註。

標準化錯誤修復審查

收集一致的偵錯報告,說明原因、修復選擇、驗證與後續工作。

Try These Prompts

開始錯誤調查
使用偵錯助理調查此問題:[描述問題]。請先詢問任何缺少的重現細節。
分析失敗的測試
針對此失敗測試使用偵錯工作流程:[測試名稱與失敗內容]。找出可能的根本原因與所需驗證。
比較修復選項
將修復產生階段套用到此根本原因:[根本原因]。比較兩種方法並建議較安全的變更。
偵錯多服務迴歸
針對此跨服務迴歸執行完整五階段偵錯流程:[事件摘要]。包含驗證與預防步驟。

Best Practices

  • 提供確切的錯誤文字、重現步驟、近期變更與受影響檔案。
  • 在接受任何產生的修復前,先執行建議的驗證測試。
  • 在啟用 shell 工作流程前,先審查命令自動化與專案設定。

Avoid

  • 在問題可重現或範圍清楚之前就變更程式碼。
  • 在未證明根本原因前抑制失敗的測試。
  • 未先審查本機設定就執行不受信任的專案測試命令。

Frequently Asked Questions

此技能可協助偵錯什麼?
它有助於調查執行階段錯誤、測試失敗、迴歸、效能問題與整合失敗。
它會自動編輯程式碼嗎?
此工作流程可以引導修復,但開發者應審查每個變更與驗證結果。
它需要 Claude Flow 嗎?
文件與 shell 命令會參照 claude-flow hooks 與記憶體,以支援協調式工作階段。
它能處理不完整的錯誤報告嗎?
可以。它會先識別缺少的症狀、重現步驟、環境詳細資訊與日誌。
團隊應如何驗證修復?
執行失敗案例、相關單元測試、整合測試,以及針對該問題新增的任何迴歸測試。
使用者在執行自動化前應審查什麼?
審查本機偵錯設定、測試命令、日誌路徑,以及任何外部工具叫用。

Developer Details

Author

DNYoussef

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

c579efd02184f1128d6741d16e6c8d951d7d4208

Maintenance freshness

7/18/2026

Usage

5 downloads · 180 views