v0.3.0 — Godot MCP Integration

[striderZA]

Summary

Godot MCP integration — provides a runtime feedback loop for automated testing and debugging.

Changes

• New automated-smoke-test skill: 7-phase workflow — verify MCP → launch project → capture debug → analyze errors → report pass/fail → cleanup
• setup-engine: Added godot-mcp installation/configuration section
• 5 agents updated with MCP capability references: gameplay-programmer, godot-gdscript-specialist, godot-specialist, ui-programmer, qa-tester
• .gitattributes: LF line ending normalization
• Docs: README (73 skills), UPGRADING.md (v0.3.0 section), setup-requirements, quick-start, skills-reference updated
• Review fixes: process cleanup, timeout/polling, heading levels, version pin, section numbering, DEBUG docs

Verification

• CI checks pass
• Review changes per commit

[github-actions]

PR Review: v0.3.0 — Godot MCP Integration

Overview

12 files changed (+354/-12). Adds an automated-smoke-test skill, godot-mCP configuration to setup-engine, MCP capability references to 5 agents, and updates to docs. Generally well-structured, but I found a few issues.

---

🐛 Bug: Contradictory skip flow in automated-smoke-test SKILL.md

File: .opencode/skills/automated-smoke-test/SKILL.md:55-58

When run_project times out (no response within 30s), the instruction says:

"Skip to Phase 6 (do not attempt stop)"

But Phase 6 (line 125-129) says:

"Call stop_project via godot-mcp to clean up."

This is contradictory — you're sent to the stop phase with instructions not to stop. The timeout case means the project is already hung/unresponsive. It should skip directly to Phase 7 (Report) , since stop_project would likely also time out.

The run_project error case (line 61-63) correctly says "Skip to Phase 7 (Report)" — the timeout path should follow the same pattern.

⚠️ Issue: Phase 4 poll error handling — ambiguous "last successful output"

File: .opencode/skills/automated-smoke-test/SKILL.md:95-96

"Once polling ends (duration elapsed or early-stop triggered), use the last successful output for analysis."

If the last poll attempt failed (3 consecutive failures triggered the skip), there is no "last successful output" to analyze. The preceding instruction already directed to skip to Phase 6 on 3 consecutive failures, so this code path would be unreachable in that specific scenario — but the wording implies there's always a "last successful output" which isn't guaranteed.

⚠️ Issue: Configuration drift in the non-contradictory section

Phase 3, line 57: For the "no response" timeout, says "Skip to Phase 6 (do not attempt stop)" — but Phase 6 unconditionally calls stop_project. If you follow line 57 literally, you'd skip the stop call. If you follow Phase 6 literally, you'd try to stop a hung project. This needs a single clear path: skip straight to Phase 7.

📝 Minor: Stale skill count in skills-reference.md

File: .opencode/docs/skills-reference.md:3

68 slash commands organized by phase

The actual count across the project is 73 (per README badges and directory). This was stale before the PR — the PR adds 1 more, bringing the effective discrepancy to 73 actual vs. 68 (now 69 with the addition). The header should say 73.

📝 Minor: qa-tester MCP wording

File: .opencode/agents/qa-tester.md:247

Use the godot-mcp server for automated smoke testing: run_project → capture debug output → check for errors

The MCP tool is get_debug_output, not "capture debug output." The agent can't literally "capture" — it calls the MCP tool. Consider: "call run_project, poll get_debug_output, and check for errors."

📝 Minor: UPGRADING.md section break placement

File: UPGRADING.md:81

The --- divider between the v0.3.0 section and the "Strategy C — Manual file copy" subsection makes Strategy C look like it's nested under v0.3.0, when it's actually a top-level strategy. Consider removing the divider or using appropriate heading levels.

---

Verdict

Category	Finding
Bugs	1 — Contradictory skip flow (timeout → Phase 6 → don't stop vs. Phase 6 → stop_project)
Warnings	1 — Ambiguous "last successful output" when all polls fail
Minor	3 — Stale count, MCP wording, divider placement

Recommendation: Fix the bug in the timeout skip flow before merging (change line 58 from "Skip to Phase 6" to "Skip to Phase 7"). The other items are non-blocking but worth addressing.

opencode session  |  github run

[striderZA]

All review items addressed:

Bug (contradictory skip flow): Fixed — timeout case now skips to Phase 7 (Report) instead of Phase 6 (stop). Phase 6 would try to stop an already-hung project, worsening the problem.

Ambiguous 'last successful output': Clarified — added 'If all polls failed (3 consecutive errors), there is no output to analyze — skip directly to the FAIL verdict.'

Stale skill count: Updated skills-reference.md from 68 to 73, and 'Claude Code' → 'OpenCode'.

qa-tester MCP wording: Changed 'capture debug output' → 'call get_debug_output'.

UPGRADING.md divider: Removed the --- separator between v0.3.0 section and Strategy C.

[github-actions]

Here's my review of the PR:

Issues from auto-review — all addressed ✓

Issue	Status
Contradictory skip flow (timeout → Phase 6 vs. Phase 6 says stop)	Fixed — now skips to Phase 7
Ambiguous "last successful output" wording	Fixed — clarifies all-polls-failed case
Stale skill count (68→73) in skills-reference.md	Fixed
qa-tester "capture debug output" → get_debug_output	Fixed
UPGRADING.md --- divider between v0.3.0 and Strategy C	Removed

Additional findings

Minor — Numbering inconsistency in setup-engine/SKILL.md: Section 7's heading ### 7.3. Configure godot-mcp uses numbered subsection prefix while its sibling subsections (### If WITHIN training data and ### If BEYOND training data) do not. This was pre-existing but the new section 7.3 deepens the inconsistency. Should be ### Configure godot-mcp (Optional — Godot Only) without the "7.3." prefix.

Minor — gameplay-programmer.md MCP wording: Line 135 says "run the project and capture debug output for iterative debugging." This is descriptive rather than tool-specific (unlike the other 4 agent files which list backtick-wrapped tool names). Not wrong, but inconsistent with the pattern used in the other agent files in this PR.

Nit — UPGRADING.md Strategy C heading level: ### Strategy C sits under ## v0.3.0, not under ## Upgrade Strategies where ### Strategy A and ### Strategy B live. Makes contextual sense (file lists precede it) but a re-reader could wonder why C lives under v0.3.0 while A/B live under Upgrade Strategies.

Verdict

Category	Count	Details
Bugs	0	All previously identified bugs fixed
Warnings	0	—
Minor	2	Section 7.3 numbering; gameplay-programmer MCP wording consistency

The code changes are clean, the new skill is well-structured with proper error handling at every phase, the agent updates are consistent, and the bot-review findings were correctly resolved. No blocking issues.

opencode session  |  github run