skills.rest
SummerEngine
SummerEngineOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debug

Diagnose and fix Summer Engine bugs through a structured listen-diagnose-hypothesize-fix-verify loop.

66|4|Updated Feb 26, 2026
Search Tags:#debugging#gdscript#godot#game engine#error diagnosis#mcp tools#runtime verification
One-click install
npx skills add https://github.com/SummerEngine/summer --skill debug-summerengine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/debug
Command: npx skills add https://github.com/SummerEngine/summer --skill debug-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game bugs in Summer Engine projects often get fixed by guesswork — agents grep codebases, edit files blindly, and declare victory without verification. This Skill enforces a disciplined debugging loop that reads the actual error first, forms one testable hypothesis, asks before editing, and re-runs the diagnostic that found the bug before claiming the fix works. ## Core Features & Use Cases - Structured diagnostic escalation: Queries script errors, diagnostics, console, and debugger errors in cheapest-first order, stopping at the first useful signal. - Runtime reproduction with probes: Drives the game itself via RunVerification probes that press inputs, sample live state, dump the running scene tree, and save frames — no user needed for gameplay bugs. - Portable support reports: Generates a Markdown debug report via summer_create_debug_report for users stuck in sandboxes or needing to send issues to Summer. - Use Case: A player falls through the floor after a scene edit. The Skill reads script errors, confirms the collider node is missing via scene inspection, proposes re-adding it versus a defensive null-check, applies the chosen fix, and re-runs a probe to verify the player lands correctly. ## Quick Start Ask the agent to debug why the game crashes when pressing jump, and have it read the debugger errors before changing any code.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a crash in a Summer Engine game project?▼

Start with summer_get_script_errors to catch parse errors, then escalate to diagnostics, console, and debugger errors in cheapest-first order. Form one specific hypothesis naming file and line, confirm it with node or resource inspection, ask before editing, and re-run the same diagnostic to verify the fix.

How to reproduce runtime-only bugs without asking the user to play?▼

Use a RunVerification probe via summer_batch to spawn a disposable game instance that presses inputs, samples live state, dumps the running scene tree, and saves frames. The returned results.errors_seen captures runtime errors without touching the user's editor session.

What if the Summer MCP tools are unavailable or the engine is not running?▼

Run summer run to start the engine, which restores every debug tool. If that is not possible, ask the user to paste the Output and Debugger panel contents and reason over the pasted text exactly as you would over MCP output.

Why does summer_set_resource_property report success but change nothing?▼

Inline sub-resource edits can silently no-op when given a JSON object instead of a Godot literal string, a misspelled subProperty, or a wrong-typed value. Pass class names and Color()/Vector3() strings, then confirm the change in the saved .tscn file rather than trusting the ok response.

When should I not use this debugging skill?▼

Skip it for design questions about preventing bug classes, feature requests with unfinished specs, and bugs in non-Godot files like CI configs or npm scripts that the host agent can debug natively. Those belong to discipline skills, make-game, or the host debugger respectively.

Related Skills

Explore More Software Engineering Skills→
AradotsoAradotso
7

godot-mcp-native

Control Godot Engine projects via MCP to generate and edit scenes, nodes, and GDScript.

Official
Advanced
OpusGameLabsOpusGameLabs
307

threejs-game

Build modular Three.js browser games with an event-driven architecture.

Official
Advanced
ZateZate
17

godot-debugging

Diagnose and fix Godot engine errors and crashes with GDScript examples.

Community
Advanced
thedivergentaithedivergentai
488

godot-debugging-profiling

Debug and profile Godot 4.x projects using breakpoints and profilers.

Community
Intermediate