一键在 Manus 中运行任何 Skill

debug-triage

星标3

分支0

更新时间2026年5月13日 16:17

Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.

安装

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

在 Manus 中运行

来源

Sagargupta16

Sagargupta16/claude-skills

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

下载

在 Manus 中运行

debug-triage

When to activate

User pastes a terminal or PowerShell transcript containing an error.
User pastes a stack trace.
User says "debug", "fix this", "why is this broken", "what's going on here".

Do NOT activate for refactoring requests, feature work, or general code review -- those are separate tasks.

Steps

Parse the actual error. Read stack traces bottom-up. The top frame is usually the symptom; the root cause is deeper in the stack or earlier in the log. Ignore generic first lines like "Traceback (most recent call last):" or "Uncaught Error".
State the likely cause in one sentence. Not a paragraph. "Null dereference on user.profile because the auth middleware returns null for unverified emails."
Propose the fix as a diff or command. Not prose. Either a code snippet showing before/after, or the exact shell command to run.
Name a regression test. Where it would live (tests/auth/email_verify_test.py), and what assertion would catch this bug next time. One line.
Flag sibling updates. If the fix changes behavior documented in README, CHANGELOG, or any doc file, list them. If not, say "none".

Rules

Don't ask the user to reformat the paste. Parse whatever they gave you.
Fix first, explain if asked. Don't narrate what the error means at length.
Ambiguous errors: if 2+ causes are equally likely, pick the likeliest and say so in one line. Do not dump all possibilities unless asked.
Recent changes are suspect. Run git log -5 --oneline -- <file> on the failing file. If a recent commit touched the failing line, mention it.
Environment first. If the error looks like it could be environmental (missing env var, wrong Node/Python version, CRLF line endings, path with spaces), check the environment before hypothesizing code bugs.

Output

Cause: <one line>
Fix: <diff or command>
Regression test: <path + what it asserts>
Siblings to update: <list or "none">

No preamble. Lead with Cause:.

同仓库更多 Skills

同仓库

clean-code

Sagargupta16/claude-skills

Use when the user writes new Python, or asks for review, refactor, or cleanup of Python code, names, comments/docstrings, functions, or tests. Applies Robert Martin's complete Clean Code catalog -- naming, functions, comments, DRY, boundary conditions, and tests -- to the code being changed.

2026-07-073

dev-rules

Sagargupta16/claude-skills

Use when writing code, making git operations, handling secrets, reviewing PRs, or working with dependencies. Enforces git safety, security best practices, PR workflow discipline, and context-efficient development patterns. Auto-activates as guardrails.

2026-07-073

motion

Sagargupta16/claude-skills

Use when reviewing motion quality, adding animation, transitions, hover effects, making the UI feel more alive, or when animations stutter and transitions jank. Covers three modes -- audit motion code against Disney's 12 principles (file:line findings), add purposeful animations and micro-interactions to a feature, or fix animation performance (layout thrashing, compositor properties, scroll-linked motion, blur).

2026-07-073

repo-polish

Sagargupta16/claude-skills

Use when setting up new repositories, auditing existing ones, or preparing repos for public visibility. Generates .gitignore, .env.example, README, and LICENSE files. Detects committed secrets and flags security issues.

2026-07-073

starter-session-audit

Sagargupta16/claude-skills

Use when the user asks to audit a session for uncaptured learnings. Activates on "audit this session", "session audit", "what did we miss", "end of session check", or "/starter-session-audit". Scans the conversation for corrections, preferences, decisions, and new context, then proposes where to save each.

2026-07-073

diff-explain

Sagargupta16/claude-skills

Use when you want a one-paragraph plain-English summary of what a diff does. Activates on "summarize this diff", "what does this PR do", "explain this branch", or when pointed at a PR URL or local branch.

2026-05-133

name	debug-triage
description	Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.
allowed-tools	Read Grep Glob Bash(git log:) Bash(git blame:) Bash(git diff:*)

debug-triage

When to activate

User pastes a terminal or PowerShell transcript containing an error.
User pastes a stack trace.
User says "debug", "fix this", "why is this broken", "what's going on here".

Do NOT activate for refactoring requests, feature work, or general code review -- those are separate tasks.

Steps

Parse the actual error. Read stack traces bottom-up. The top frame is usually the symptom; the root cause is deeper in the stack or earlier in the log. Ignore generic first lines like "Traceback (most recent call last):" or "Uncaught Error".
State the likely cause in one sentence. Not a paragraph. "Null dereference on user.profile because the auth middleware returns null for unverified emails."
Propose the fix as a diff or command. Not prose. Either a code snippet showing before/after, or the exact shell command to run.
Name a regression test. Where it would live (tests/auth/email_verify_test.py), and what assertion would catch this bug next time. One line.
Flag sibling updates. If the fix changes behavior documented in README, CHANGELOG, or any doc file, list them. If not, say "none".

Rules

Don't ask the user to reformat the paste. Parse whatever they gave you.
Fix first, explain if asked. Don't narrate what the error means at length.
Ambiguous errors: if 2+ causes are equally likely, pick the likeliest and say so in one line. Do not dump all possibilities unless asked.
Recent changes are suspect. Run git log -5 --oneline -- <file> on the failing file. If a recent commit touched the failing line, mention it.
Environment first. If the error looks like it could be environmental (missing env var, wrong Node/Python version, CRLF line endings, path with spaces), check the environment before hypothesizing code bugs.

Output

Cause: <one line>
Fix: <diff or command>
Regression test: <path + what it asserts>
Siblings to update: <list or "none">

No preamble. Lead with Cause:.