菜单
Investigate bugs, errors, or unexpected behaviour — reproduce, isolate, diagnose, and fix. Use when given an error message, stack trace, "works in staging but not prod", or "broke after deploy". Do NOT use for incident response workflows, code review (code-review), or implementation (implement).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Instance bootstrap interview — detects existing instance state, guides repo creation (link-first), interviews business identity/services/cadence/targets, writes config/instance.json and target skeletons, then hands off to brand-creative setup. Use on first install, when the user says "set up my instance" or "bootstrap my agency workspace", or to re-check target bindings after config changes.
Create a competitive analysis brief for product strategy, feature prioritization, or sales enablement. Use when comparing competitors, mapping a feature area across rivals, or drafting battle cards. Do NOT use for user research synthesis (synthesize-research) or product strategy doc (product).
Run a weekly, monthly, or quarterly metrics review: scorecard, trends, bright spots, concerns, and recommended actions. Use when investigating a spike or drop, comparing performance against targets, or preparing a metrics readout. Do NOT use for stakeholder status updates (stakeholder-update) or product strategy (product).
Sparring partner for exploring a problem space, generating solutions, or stress-testing product thinking. Conversation, not a deliverable. Use when ideating, assumption-testing, or strategy exploration before a spec. Do NOT use for writing specs (write-spec) or product strategy doc (product).
Write a weekly or monthly status for leadership, announce a launch, escalate a risk, or tailor the same progress for exec, engineering, partner, customer, or board audiences. Use when drafting status updates or launch notes. Do NOT use for product strategy (product) or roadmap updates (roadmap).
Synthesize interview notes, survey data, or support tickets into themes, personas, opportunity areas, and roadmap recommendations. Use when turning raw research into structured findings. Do NOT use for competitive analysis (competitive-brief) or product strategy doc (product).
基于 SOC 职业分类
| name | debug |
| description | Investigate bugs, errors, or unexpected behaviour — reproduce, isolate, diagnose, and fix. Use when given an error message, stack trace, "works in staging but not prod", or "broke after deploy". Do NOT use for incident response workflows, code review (code-review), or implementation (implement). |
| license | MIT |
| allowed-tools | Read Write Glob Grep Bash |
| argument-hint | <error message or problem description> |
| metadata | {"author":"Carinya Parc","version":"0.1.0","owner":"web-development","review_cadence":"as-needed","work_shape":"targeted-change","output_class":"code-change"} |
Structured debugging — reproduce, isolate, diagnose, and fix. Pass the error message, stack trace, or problem description after the skill name.
See CONNECTORS.md for monitoring and source-control tools.
If monitoring is connected: pull logs, error rates, and metrics around the issue time; correlate with recent deploys. If source control is connected: identify commits/PRs on affected paths. If project tracker is connected: search related bugs; create a ticket for the fix once identified.
## Debug Report: [Issue Summary]
### Reproduction
- **Expected**: …
- **Actual**: …
- **Steps**: …
### Root Cause
…
### Fix
…
### Prevention
- [Test to add]
- [Guard to put in place]