一键在 Manus 中运行任何 Skill

common-debugging

星标533

分支154

更新时间2026年7月14日 18:20

Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

HoangNguyen0403

HoangNguyen0403/agent-skills-standard

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Debugging Expert

Priority: P1 (HIGH)

Root-Cause Protocol

OBSERVE: Gather error, logs, repro steps, recent diffs.
REPRODUCE: Make the failure happen on demand or gather more evidence.
HYPOTHESIZE: State one hypothesis in plain language.
EXPERIMENT: Change one variable to prove or kill the theory.
FIX: Touch code only after root cause proven.
VERIFY: Re-run the failing case and regression checks.

Red Flags

Stop if you are changing code before repro: You are guessing.
Stop if fix #2 starts before understanding fix #1: Re-open root cause.
Stop if "quick patch for now" appears: Symptom masking starts there.

Rationalization Prevention

"The bug is obvious": Obvious bugs still need evidence.
"I already tried a few things": That means you need structure.
"It only fails in prod": Gather prod evidence, do not invent local myths.
Minimal repro first: A minimal reproduction beats more random fixes.

Anti-Patterns

No shotgun debugging: Prove root cause before changing code.
No debug prints in production: Remove all print/console.log before commit.
No symptom masking: Fix root cause; never swallow errors without handling.

References

Bug Report Template

Incident pressure checklist

For production incidents, reproduce with a production-like replay and state one hypothesis before changing code; stop symptom patches until the root cause is proven.

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

hypothesis
one hypothesis
stop
Additional task-grounded exact anchors: minimal

同仓库更多 Skills

同仓库

common-best-practices

HoangNguyen0403/agent-skills-standard

Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.

2026-07-14533

common-code-review

HoangNguyen0403/agent-skills-standard

Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.

2026-07-14533

common-context-optimization

HoangNguyen0403/agent-skills-standard

Maximize context window efficiency, reduce latency, and prevent lost-in-middle issues through strategic masking and compaction. Use when token budgets are tight, tool outputs overflow the context, conversations drift from intent, or latency spikes from cache misses.

2026-07-14533

common-dast-tooling

HoangNguyen0403/agent-skills-standard

Standardize dynamic application security testing for backend APIs, frontend web apps, and mobile clients. Covers ZAP, Nuclei, Nikto, sqlmap, ffuf, browser automation, mobile proxy interception, and AI-driven curl probes. Use when advising on or running dynamic security scans on local/staging environments.

2026-07-14533

common-documentation

HoangNguyen0403/agent-skills-standard

Write effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.

2026-07-14533

common-feedback-reporter

HoangNguyen0403/agent-skills-standard

Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.

2026-07-14533

name	common-debugging
description	Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.
metadata	{"triggers":{"keywords":["debug","fix bug","crash","error","exception","troubleshooting"]}}

Debugging Expert

Priority: P1 (HIGH)

Root-Cause Protocol

OBSERVE: Gather error, logs, repro steps, recent diffs.
REPRODUCE: Make the failure happen on demand or gather more evidence.
HYPOTHESIZE: State one hypothesis in plain language.
EXPERIMENT: Change one variable to prove or kill the theory.
FIX: Touch code only after root cause proven.
VERIFY: Re-run the failing case and regression checks.

Red Flags

Stop if you are changing code before repro: You are guessing.
Stop if fix #2 starts before understanding fix #1: Re-open root cause.
Stop if "quick patch for now" appears: Symptom masking starts there.

Rationalization Prevention

"The bug is obvious": Obvious bugs still need evidence.
"I already tried a few things": That means you need structure.
"It only fails in prod": Gather prod evidence, do not invent local myths.
Minimal repro first: A minimal reproduction beats more random fixes.

Anti-Patterns

No shotgun debugging: Prove root cause before changing code.
No debug prints in production: Remove all print/console.log before commit.
No symptom masking: Fix root cause; never swallow errors without handling.

References

Bug Report Template

Incident pressure checklist

For production incidents, reproduce with a production-like replay and state one hypothesis before changing code; stop symptom patches until the root cause is proven.

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

hypothesis
one hypothesis
stop
Additional task-grounded exact anchors: minimal