Menu
Systematic debugging with persistent state across context resets
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Use this skill when the user wants direct operations on an Obsidian vault: read or edit notes and daily notes, search vault contents, count or list notes, manage tasks, move or rename files, find orphaned notes or broken links, inspect frontmatter/properties, manage sync or file history, query Bases, manage bookmarks, script the CLI, or run JavaScript against the Obsidian API. Trigger when the request implies "go into my vault and do X"; the user wants action on vault data, not an explanation. Skip pure conceptual or GUI-help questions such as settings navigation, theme/plugin installation, sync troubleshooting, Dataview syntax, keyboard shortcuts, or parsing vault files with unrelated external scripts.
Captures corrections, failures, missing capabilities, and reusable discoveries in agent so future work improves. Use this skill whenever a command, tool, or API fails unexpectedly; the user corrects the agent; the agent realizes its knowledge is outdated or wrong; a missing capability is exposed; or a better recurring approach is discovered. Record the result under .agents/learnings/, review related entries before major tasks, and promote durable workflow rules into AGENTS.md when they should change future behavior.
Generate tests for a completed phase based on UAT criteria and implementation
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
| name | gsd-debug |
| description | Systematic debugging with persistent state across context resets |
Orchestrator role: Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations.
Flags:
--diagnose — Diagnose only. Returns a Root Cause Report without applying a fix.Subcommands: list · status <slug> · continue <slug>
<available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
<execution_context> @/home/aming/.config/opencode/gsd-core/workflows/debug.md </execution_context>
User's input: $ARGUMENTSParse subcommands and flags from $ARGUMENTS BEFORE the active-session check:
--diagnose: SUBCMD=debug, diagnose_only=true, strip --diagnose from descriptionCheck for active sessions (used for non-list/status/continue flows):
ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5