- Home
- Skills
- Game Development
- graphify gdscript
graphify gdscript
Map Godot project architectures and trace signal connections across scenes and scripts using a local knowledge graph.
Free
Works with the AI Agents you already use
graphify gdscript
Example session with this skill installed
/graphify-gdscript trace "health_changed"
- Read your context and instructions
- Compiled the graphify gdscript
I have traced the health_changed signal across the project. It is declared in the HealthComponent, emitted during damage calculation, and connected to the UI overlay via the Game.tscn scene file.
Signal Trace: health_changed
| Relation | Source | Target | Context |
|---|---|---|---|
| declares_signal | scripts/components/health.gd:L5 | health_changed | signal health_changed(old, new) |
| emits | scripts/components/health.gd:L42 | health_changed | health_changed.emit(prev, current) |
| connects_to | scenes/entities/player.tscn:L112 | scripts/ui/health_bar.gd:L15 | Signal bound in Scene Tree to _on_health_changed |
| connects_to | scenes/main/game.tscn:L405 | scripts/managers/sfx_manager.gd:L88 | Connected via inspector to play hit sounds |
| calls | scripts/ui/health_bar.gd:L16 | update_visuals() | Callback logic execution |
Gaps
- The graph did not find any dynamic connections via
connect()calls in theLevelManagerscript, which may exist but are not statically reachable.
Next steps
- If you need to refactor the signal arguments, start with the declaration in
scripts/components/health.gd:L5. - Update the callback signature in
scripts/ui/health_bar.gd:L15to match. - Run
gdscript_rebuild_graphafter saving changes to verify connections.
Connects securely to your tools. The creator never sees your data.
About this skill
Godot projects often become a tangled web of scene tree dependencies, signal connections, and autoload singletons that standard grep searches fail to map. This skill parses your project into a comprehensive knowledge graph, revealing the hidden links between .tscn files and .gd scripts that lead to "spaghetti" architecture.
What it does
- Signal Tracing maps every declaration, emission, and connection, including those hidden inside scene files.
- Autoload Analysis resolves singleton calls to their underlying scripts and tracks global state usage.
- Pathfinding calculates the shortest connection between two arbitrary symbols to explain how systems interact.
- Token Optimization generates high-context subgraphs for LLM queries, reducing token usage compared to repo-wide searches.
- Architecture Auditing identifies "god nodes" and tightly coupled communities within your game logic.
How it works
- Run
/graphify-gdscriptto perform an AST-based scan of your project files and build the local graph database. - Use
query "<question>"to retrieve a cited subgraph that answers specific architectural or logic questions. - Use
trace "<signal>"to find every instance of a signal across both scripts and scene files. - Execute
path "<A>" "<B>"to see the exact chain of calls or references linking two parts of your codebase.
Frameworks & tools
Built for Godot 3.x and 4.x projects. It requires the graphify-gdscript Python CLI tool and can integrate with an MCP server for tool-calling environments.
Why this beats prompting it yourself
Standard LLMs struggle with Godot's multi-file nature, often missing signal connections defined in .tscn binary/text formats. This skill uses a local AST parser to provide ground-truth citations, ensuring the agent doesn't hallucinate node paths or invisible connections.
Use cases
- Debugging why a signal isn't triggering a specific callback in a complex UI scene.
- Mapping the dependencies of a legacy Autoload before refactoring it into a resource-based system.
- Explaining the initialization order and node references of a deeply nested player scene.
- Generating a token-efficient architecture report for a new developer onboarding to the project.
Known limitations
Cannot track dynamic connect() calls made with string-based names or node paths constructed via runtime string manipulation. Requires a local Python environment.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.
Cannot track dynamic connect() calls or node paths built at runtime via strings. Requires local Python 3.9+ and the graphify-gdscript CLI installed on PATH.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 3 days ago
- Free with an Agensi account
- Software
Python