Vibe Reflect And Compound
ash1794/vibe-engineering
Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent…
Systematic debugging with persistent state across context resets
Install Gsd Debug
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-debug --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/gsd-debug .claude/skills/gsd-debug && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gsd-debug" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-debug into .claude/skills/gsd-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-debug", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-debugType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/gsd-debug .agents/skills/gsd-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gsd-debug" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-debug into .agents/skills/gsd-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-debug", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/gsd-debug .cursor/skills/gsd-debug && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gsd-debug" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-debug into .cursor/skills/gsd-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-debug", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SpillwaveSolutions/agent-brain.git --path .codex/skills/gsd-debug--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/gsd-debug .gemini/skills/gsd-debug && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gsd-debug" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-debug into .gemini/skills/gsd-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-debug", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SpillwaveSolutions/agent-brain gsd-debugInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/gsd-debug .github/skills/gsd-debug && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gsd-debug" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-debug into .github/skills/gsd-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-debug", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/gsd-debug .opencode/skills/gsd-debug && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gsd-debug" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-debug into .opencode/skills/gsd-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-debug", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gsd-debug- GitHub stars
- 120
- Used in
- 4 other repos
- Token cost
- ~1.5k tokens
- SKILL.md length
- 519 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Systematic debugging with persistent state across context resets
- Works in 6 steps: Initialize Context → Check Active Sessions → Gather Symptoms (if new issue) → …
- Tasks that involve Debugging
- SKILL.md covers A. Skill Invocation, B. AskUserQuestion →…, C. Task() → spawn_agent Mapping and 0. Initialize Context, plus 5 more sections
- Calls node
What it does
Gsd Debug is an agent skill from SpillwaveSolutions/agent-brain. Systematic debugging with persistent state across context resets
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Debugging and Agent memory. The repository describes itself as: Local-first RAG memory for AI agents: hybrid + GraphRAG search, MCP server with OAuth 2.1, plugin for Claude Code / OpenCode / Codex. The licence is MIT.
When your agent uses it
- Tasks that involve Debugging
- Tasks that involve Agent memory
Example prompts
- “/gsd-debug”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8339623. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gsd Debug loads about 1.5k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 519 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SpillwaveSolutions/agent-brain at commit 8339623, republished under its MIT licence (© SpillwaveSolutions). 519 words, ~1,486 tokens.
Download SKILL.mdSave it as
.claude/skills/gsd-debug/SKILL.md (or your agent's skills folder).- name
- gsd-debug
- description
- Systematic debugging with persistent state across context resets
- metadata.short-description
- Systematic debugging with persistent state across context resets
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-debug. - Treat all user text after
$gsd-debugas{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_inputis rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y")→spawn_agent(agent_type="X", message="Y")Task(model="...")→ omit (Codex uses per-role config, not inline model selection)fork_context: falseby default — GSD agents load their own context via<files_to_read>blocks
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids)for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT,PLAN COMPLETE,SUMMARY, etc. close_agent(id)after collecting results from each agent </codex_skill_adapter>
<objective>
Debug issues using scientific method with subagent isolation.Orchestrator role: Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations.
Why subagent: Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction.
</objective>
<available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
- gsd-debugger — Diagnoses and fixes issues </available_agent_types>
<context>
User's issue: {{GSD_ARGS}}Check for active sessions:
ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5</context><process>0. Initialize Context
INIT=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" state load)
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fiExtract commit_docs from init JSON. Resolve debugger model:
debugger_model=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-debugger --raw)1. Check Active Sessions
If active sessions exist AND no {{GSD_ARGS}}:
- List sessions with status, hypothesis, next action
- User picks number to resume OR describes new issue
If {{GSD_ARGS}} provided OR user describes new issue:
- Continue to symptom gathering
Show full SKILL.md (196 more words)Show less
2. Gather Symptoms (if new issue)
Use AskUserQuestion for each:
- Expected behavior - What should happen?
- Actual behavior - What happens instead?
- Error messages - Any errors? (paste or describe)
- Timeline - When did this start? Ever worked?
- Reproduction - How do you trigger it?
After all gathered, confirm ready to investigate.
3. Spawn gsd-debugger Agent
Fill prompt and spawn:
<objective>
Investigate issue: {slug}
**Summary:** {trigger}
</objective>
<symptoms>
expected: {expected}
actual: {actual}
errors: {errors}
reproduction: {reproduction}
timeline: {timeline}
</symptoms>
<mode>
symptoms_prefilled: true
goal: find_and_fix
</mode>
<debug_file>
Create: .planning/debug/{slug}.md
</debug_file>Task(
prompt=filled_prompt,
subagent_type="gsd-debugger",
model="{debugger_model}",
description="Debug {slug}"
)4. Handle Agent Return
If ## ROOT CAUSE FOUND:
- Display root cause and evidence summary
- Offer options:
- "Fix now" - spawn fix subagent
- "Plan fix" - suggest $gsd-plan-phase --gaps
- "Manual fix" - done
If ## CHECKPOINT REACHED:
- Present checkpoint details to user
- Get user response
- If checkpoint type is
human-verify:- If user confirms fixed: continue so agent can finalize/resolve/archive
- If user reports issues: continue so agent returns to investigation/fixing
- Spawn continuation agent (see step 5)
If ## INVESTIGATION INCONCLUSIVE:
- Show what was checked and eliminated
- Offer options:
- "Continue investigating" - spawn new agent with additional context
- "Manual investigation" - done
- "Add more context" - gather more symptoms, spawn again
5. Spawn Continuation Agent (After Checkpoint)
When user responds to checkpoint, spawn fresh agent:
<objective>
Continue debugging {slug}. Evidence is in the debug file.
</objective>
<prior_state>
<files_to_read>
- .planning/debug/{slug}.md (Debug session state)
</files_to_read>
</prior_state>
<checkpoint_response>
**Type:** {checkpoint_type}
**Response:** {user_response}
</checkpoint_response>
<mode>
goal: find_and_fix
</mode>Task(
prompt=continuation_prompt,
subagent_type="gsd-debugger",
model="{debugger_model}",
description="Continue debug {slug}"
)</process><success_criteria>
- Active sessions checked
- Symptoms gathered (if new)
- gsd-debugger spawned with context
- Checkpoints handled correctly
- Root cause confirmed before fixing </success_criteria>
© SpillwaveSolutions, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .codex/skills/gsd-debug of SpillwaveSolutions/agent-brain.
Open the folder on GitHubat commit 8339623
Used in 4 other repositories
We found 15 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in SpillwaveSolutions/agent-brain, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Gsd Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gsd Debug this skillSpillwaveSolutions/agent-brain | 120 | 4 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Vibe Reflect And Compoundash1794/vibe-engineering | 162 | — | ~864 | Automated safety check: Pass | MIT | |
| Cuda Cpp Kernelvipshop/cache-dit | 1.3k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| CodeNavitech-leads-club/agent-skills | 7k | — | ~3.4k | Automated safety check: Pass | CC-BY-4.0 | |
| Learning LoopLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 97k | 1 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cuda Cpp Kernel
vipshop/cache-dit
A skill your agent uses when writing, debugging, porting, reviewing, or optimizing CUDA C++ or PTX kernels; investigating CUDA Runtime or Driver API behavior; profiling kernels with Nsight Systems…
CodeNavi
tech-leads-club/agent-skills
Investigates unfamiliar codebases before changing them, makes small targeted edits and records what it learns in a .notebook/ folder for later sessions.
Learning Loop
LeoYeAI/openclaw-master-skills
Structured self-improvement system for AI agents with confidence decay, cross-agent sharing, and anomaly detection.
Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
More from SpillwaveSolutions/agent-brain
All 55 skills in this repoGsd Complete Milestone
SpillwaveSolutions/agent-brain
Archive completed milestone and prepare for next version. An agent skill from SpillwaveSolutions/agent-brain.
Mastering Python Skill
SpillwaveSolutions/agent-brain
Modern Python coaching covering language foundations through advanced production patterns.
Gsd Review Backlog
SpillwaveSolutions/agent-brain
Review and promote backlog items to active milestone. An agent skill from SpillwaveSolutions/agent-brain.
Configuring Agent Brain
SpillwaveSolutions/agent-brain
Installation and configuration skill for Agent Brain document search system.
Gsd Thread
SpillwaveSolutions/agent-brain
Manage persistent context threads for cross-session work. An agent skill from SpillwaveSolutions/agent-brain.
Gsd Plant Seed
SpillwaveSolutions/agent-brain
Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
Related
Categories
Questions about Gsd Debug
What does Gsd Debug do?
Systematic debugging with persistent state across context resets. Gsd Debug is an agent skill from SpillwaveSolutions/agent-brain.
When should I use Gsd Debug?
Gsd Debug fits situations like: tasks that involve Debugging; tasks that involve Agent memory.
How do I install Gsd Debug in Claude Code?
Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a claude-code`. Or copy the skill folder (.codex/skills/gsd-debug in SpillwaveSolutions/agent-brain) into .claude/skills/gsd-debug in your project. Claude Code loads it when a task matches its description.
How do I install Gsd Debug in Codex?
Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a codex`. Or copy the skill folder (.codex/skills/gsd-debug in SpillwaveSolutions/agent-brain) into .agents/skills/gsd-debug in your project. Codex loads it when a task matches its description.
Can I use Gsd Debug in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsd-debug, .gemini/skills/gsd-debug, .github/skills/gsd-debug and .opencode/skills/gsd-debug in your project.
What does Gsd Debug need to run?
Going by SKILL.md and its folder, Gsd Debug needs the command-line tools its instructions call (node).
Does Gsd Debug access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Gsd Debug safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gsd Debug use?
Gsd Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gsd Debug use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gsd Debug?
Skills that share tags, products or a category with Gsd Debug: Vibe Reflect And Compound (ash1794/vibe-engineering, 162 stars), Cuda Cpp Kernel (vipshop/cache-dit, 1.3k stars), CodeNavi (tech-leads-club/agent-skills, 7k stars) and Learning Loop (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gsd Debug?
SpillwaveSolutions (a GitHub organization) maintains it in SpillwaveSolutions/agent-brain, which has 120 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 19, 2026.
Source: SpillwaveSolutions/agent-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.