audio-review

Review Godot audio code for engine gotchas and report fixes.

511|44|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill audio-review-randallliuxin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audio-review
Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/reviewer/audio
Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill audio-review-randallliuxin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents common Godot 4.x audio issues by reviewing implemented audio code for design-level gotchas that lead to memory blowups, missing sounds, unstable bus changes, or broken playback sequencing.

Core Features & Use Cases

  • Audio gotcha scanning: Checks for known pitfalls triggered by AudioStreamPlayer/2D/3D usage, AudioServer bus structural changes, compressed stream preloads, and finished-signal usage on audio players.
  • Actionable remediation: For each detected gotcha, it reports the gotcha ID, shows the offending code, and provides a concrete fix aligned with Godot’s intended behavior.
  • Automated verification hooks: Optionally runs checklist-driven static and runtime checks, including polyphony stress and lifecycle behavior around finished signals.

Use case: after an agent implements sound effects and audio buses, run this reviewer to ensure short critical SFX are not cut by polyphony limits, compressed OGG/MP3 assets are not over-preloaded, AudioServer bus modifications are correctly lock-guarded, and composite/looping streams do not rely on finished.

Quick Start

Use the audio-review skill after the Godot audio implementation is complete to scan the project for gotchas and produce a fix list.

Frequently Asked Questions about audio-review

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

FAQPage Schema
How do I review Godot audio code for memory overruns and missing sounds?

Review Godot audio code by scanning AudioStreamPlayer nodes and AudioServer bus operations for common engine gotchas that cause memory overruns, missing sounds, and unstable bus manipulation. The review maps detected issues to specific gotcha IDs and provides concrete fixes.

Why do my Godot short SFX get cut when using polyphony limits?

Short SFX get cut by polyphony limits when AudioStreamPlayer configuration exceeds voice caps. An audio review checks polyphony stress and flags critical sound effects vulnerable to cutoff, ensuring playback reliability under concurrent audio loads.

How do I handle AudioServer bus locking to prevent unstable changes in Godot?

AudioServer bus modifications require lock-guarded operations to prevent structural instability. An audio review detects unguarded bus manipulation code and enforces correct lock usage, mapping offending code to gotcha IDs with explicit lifecycle guidance.

Why should I not rely on the finished signal for Godot looping or composite audio playback?

The finished signal is unreliable for looping or composite audio playback due to lifecycle timing issues. An audio review identifies incorrect finished-signal wiring on audio players and requires explicit lifecycle handling for robust playback sequencing.

Can I check if compressed OGG or MP3 assets are being over-preloaded in Godot?

Yes, compressed OGG and MP3 audio preloads can be checked for memory blowups. An audio review scans for compressed stream preload patterns that cause memory overruns, flags offending code, and provides concrete fixes aligned with Godot's intended behavior.

When should I run an audio gotcha scan on my Godot project?

Run an audio gotcha scan after audio implementation is complete or modified, specifically when AudioStreamPlayer nodes, AudioServer operations, or compressed preloads are present. It produces a fix list mapping detected gotchas to remediation steps before release.