game-refactor

To batch refactor GDScript code quality, run /game-refactor after /game-verify to analyze feature.json-defined pipelines in parallel and generate a unified plan with per-feature changes and rollback options.

Identifying cross-feature refactor opportunities in a Godot project involves parallel analysis of feature pipelines, prioritizing high-impact issues like security, memory, and performance to consolidate findings into a single approval workflow.

Yes, you can restrict GDScript refactoring to only pipeline files by enforcing strict boundaries that modify only files listed in feature.json, ensuring unrelated files remain completely untouched during the batch process.

Yes, you need to run /game-verify before starting the batch Godot code refactoring workflow, as /game-refactor is designed to process feature pipelines only after a successful verification phase.

The unified Godot refactor plan handles rollback and traceability by producing per-feature diffs and recording results in .project/session and feature.json.refactor metadata, ensuring every change is tracked and reversible.

High-impact code quality issues prioritized during Godot pipeline refactoring include security vulnerabilities, memory leaks, and performance bottlenecks, which are addressed before generating the unified plan across all queued features.