القائمة
Hypothesis-first bug diagnosis. Verify the user's diagnosis before proposing alternatives. Keywords: bug, diagnose, debug, fix, hypothesis, root cause, crash, error, timeout, traceback.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Query SwanLab experiment metrics and run status. Use when checking training/producer metrics, comparing runs, or investigating experiment health. Keywords: swanlab, metrics, experiment, loss, reward, training progress, wandb.
Launch a background agent to monitor a long-running remote job (K8s, SLURM, CI). Use when submitting jobs that need async monitoring. Keywords: monitor, watch job, background agent, submit and watch, check job status.
Generate a weekly report summarizing commits and PRs across the main repo and all external/ submodules. Keywords: weekly report, 周报, work summary, 工作总结.
Capture reusable knowledge after milestones. Systematically review what was learned and persist it to the right layer. Keywords: sediment, crystallize, capture, persist, remember, learned, milestone, retrospective.
Build a first-failure timeline for distributed incidents. Use when debugging crashes, hangs, watchdog timeouts, collective mismatches, or cascading errors where the last error is often not the root cause.
Convert local debugging results into high-quality upstream issues or RFC comments. Use when filing bugs to external projects with clear reproduction, first-failure evidence, root-cause hypothesis, and scoped fix suggestions.
| name | diagnose-bug |
| description | Hypothesis-first bug diagnosis. Verify the user's diagnosis before proposing alternatives. Keywords: bug, diagnose, debug, fix, hypothesis, root cause, crash, error, timeout, traceback. |
Structured debugging workflow that respects the user's diagnosis.
/diagnose-bug <error message>
Hypothesis: <your diagnosis>
Check: <specific file/function to verify>
Verify the user's hypothesis FIRST. Read the specified file/function, check git history, trace the code path. Do not propose alternative theories until the hypothesis is confirmed or ruled out.
If confirmed: Implement the minimal fix. No refactoring, no cleanup, no "while we're here" improvements.
If ruled out: Explain concretely why (show the code path that contradicts it), then propose ONE alternative hypothesis and verify it the same way.
Never skip straight to a fix without showing evidence that the root cause is understood.