一键导入
dev-debug
Debug an issue by identifying root causes, fixing the most probable one, testing, and committing. Use with "/dev-debug <description of the issue>".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Debug an issue by identifying root causes, fixing the most probable one, testing, and committing. Use with "/dev-debug <description of the issue>".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Search for a product across multiple retailers in parallel, save pricing data to disk, and produce an HTML report with the best deals and direct product links. Use when the user asks to compare prices, find the best deal, or check prices across stores.
Research a topic across multiple sources using parallel tabs, save raw content and findings to files, then produce an HTML report and PDF. Use when the user asks to research, investigate, or gather information on a topic.
Extract structured data from web pages — tables, lists, product info, pricing — into clean CSV, JSON, or markdown tables. Parallelizes across hidden tabs for multi-source extraction and saves results to disk incrementally. Use when the user asks to scrape, extract, or pull data from a page.
Find alternative products to something the user is looking at or considering. Searches across retailers and review sites, compares options, and delivers a ranked HTML report with ratings, pricing, and direct links. Use when the user asks for alternatives, similar products, or "something like this but..."
Bookmark the current page to a "📚 Read Later" folder and save a PDF copy for offline reading. Use when the user wants to save a page for later, bookmark it for reading, or keep an offline copy.
Save web pages as PDF files for offline reading, archiving, or sharing. Use when the user asks to save, download, export, or archive a page as PDF.
基于 SOC 职业分类
| name | dev-debug |
| description | Debug an issue by identifying root causes, fixing the most probable one, testing, and committing. Use with "/dev-debug <description of the issue>". |
| disable-model-invocation | true |
| argument-hint | ["issue description"] |
You are debugging an issue. Be methodical — understand before you fix.
login_redirect_fail).llm/debug_<slug>/ directory$ARGUMENTS.Write your analysis to .llm/debug_<slug>/tmp_root_causes.md:
## Issue
<restate the issue clearly>
## Root Causes (ranked by probability)
### 1. [Most likely] — <short title>
- **Why**: Explanation of why this could be the cause
- **Evidence**: What in the code supports this theory
- **Files**: Relevant file paths
### 2. <short title>
...
Present the root causes to the user. Ask if they agree with the ranking or want to override which one to fix first.
After user confirms (or you proceed with #1 by default):
Stage and commit the fix:
git add -A && git commit -m "fix: <concise description of what was fixed and why>"
If the fix didn't fully resolve the issue (or if there are related problems):
.llm/debug_<slug>/tmp_root_causes.md — mark #1 as addressed, re-rank remaining causesWhen the issue is resolved, tell the user:
Debug complete. Fixed in N commit(s). See
.llm/debug_<slug>/tmp_root_causes.mdfor the full analysis.