release: v0.6.0 — Aseprite MCP workflow

[striderZA]

Summary

• Aseprite MCP integration: Submodule, MCP config, art-generate skill, and integration design doc for programmatic placeholder art via CLI
• Workflow Selection Gate: Hybrid vs Full OCGS workflow choice at project start (Path D/E)
• Art Bible machine export: Palette, typography, AI prompts, and reference catalog in structured formats
• Workflow integrity test suite: Cross-reference, path, gate, and invariant validation (129+ plugin tests)
• Skill testing framework: Fixed paths, registered missing skills, CI validation
• Move ISSUE_TEMPLATE to correct .github/ location + add feature request docs

Test Plan

• Agent validation: 179/179 passed
• Plugin test suite: 129+ tests across 11 suites all pass
• Smoke check: All cross-references, paths, gates, invariants validated

[github-actions]

Code Review: PR # — release: v0.6.0

I reviewed 77 changed files. Here's the assessment:

Quality Issues

Issue	File	Severity
Hardcoded Windows dev paths	opencode.json:17,25 — E:\Jaco\... paths for ASEPRITE_PATH and GODOT_PATH	High — breaks on non-Windows and any machine but the author's
Test runner lacks timeout	tests/workflow/run-all.mjs — fork() with no kill timer; a hung suite hangs CI indefinitely	Medium
--no-sync on Aseprite MCP	opencode.json:14 — uv run --no-sync will fail if .venv not pre-built; no error recovery	Medium
Shell command in skill frontmatter	.opencode/skills/help/SKILL.md:8 — context: | !echo "=== Live Project State ==="... — this worked as a Claude Code hook but OpenCode treats context as static text, not shell execution	Low (dead code)

Potential Bugs

Bug	Details	Risk
ISSUE_TEMPLATE migration is partial	Deletes bug-report.md and config.yml from wrong dir (.github/workflows/ISSUE_TEMPLATE/) but only adds feature-request.md to correct dir (.github/ISSUE_TEMPLATE/). Bug report template is lost entirely — no replacement created.	High
Submodule not initialized in CI	.gitmodules references tools/aseprite-mcp but agent-validation.yml never runs git submodule update --init. The validate-workflow job will work (no submodule dep), but actual MCP usage will fail.	Medium
Session state dirs gitignored but workflow expects them	production/session-state/ is gitignored, but start skill writes production/stage.txt during onboarding. If production/ dir doesn't exist yet, the write fails	Low (mkdir handles it)

Suggestions

1. Make Aseprite/Godot paths configurable in opencode.json — use env vars with sensible fallbacks:

   "environment": {
     "ASEPRITE_PATH": "${ASEPRITE_PATH:-aseprite}"
   }

2. Add timeout to fork-based test runner:

   const timer = setTimeout(() => { child.kill(); reject('timeout'); }, 30000);

3. Restore bug-report.md at .github/ISSUE_TEMPLATE/bug-report.md — the deletion removes it entirely without replacement.

4. Add git submodule update --init to the CI workflow before running validation.

5. Either remove --no-sync or add a setup step for the Aseprite MCP venv. Document in the design doc that uv sync must be run after submodule init.

6. Fix help skill context — either remove the dead shell command or use a proper OpenCode mechanism for dynamic context injection.

Summary

The PR is broad in scope and well-structured. The Aseprite MCP integration, workflow selection gate, art bible exports, and test suite are solid contributions. The main blockers are the missing bug-report.md (lost on deletion) and hardcoded Windows paths that make the MCP config non-portable. The test runner timeout and submodule CI init are medium-priority fixes.

opencode session  |  github run

[github-actions]

Code Review: v0.6.0 — Aseprite MCP Workflow

I examined all 19 changed files. Here's my assessment:

---

Verified: Previously Flagged Issues Already Addressed

Several issues raised in the prior CI review were already fixed in the committed code:

Claimed Issue	Actual State
Hardcoded Windows paths in opencode.json	Uses {env:ASEPRITE_PATH} / {env:GODOT_PATH} — portable
--no-sync on MCP command	Committed version omits --no-sync — auto-syncs
Missing test timeout	tests/workflow/run-all.mjs has SUITE_TIMEOUT=30000 with setTimeout/kill
help skill shell command	Frontmatter is static text: "Static help skill..."
Submodule not in CI	actions/checkout@v4 with submodules: recursive handles it
bug-report.md "lost entirely"	Successfully renamed (moved) to .github/ISSUE_TEMPLATE/bug-report.md — content intact

---

Actual Issues Found

#	Issue	File	Severity
1	Inconsistent MCP env var key	opencode.json:16 vs :24 — "environment" for aseprite, "env" for godot. Different keys may silently drop one set of variables depending on which key OpenCode's MCP runner actually reads.	High
2	config.yml deleted without replacement	.github/workflows/ISSUE_TEMPLATE/config.yml deleted (+0/-8). No new config.yml created at .github/ISSUE_TEMPLATE/config.yml. This disables contact links and blank-issue controls.	Medium
3	New skills registered with empty specs	catalog.yaml:789-842 — art-generate, explore, hybrid-prototype, automated-smoke-test, init-template all have spec: "". These skills won't have behavioral test coverage in the skill-testing framework.	Medium
4	PowerShell Test-Path in skill instructions	.opencode/skills/art-generate/SKILL.md:181 — Phase 2g verification says Test-Path "assets/sprites/...". This is PowerShell-specific and won't execute on Linux/macOS. Should use test -f or a generic file-exists check.	Medium
5	Plan doc hardcoded to Windows	framework/docs/superpowers/plans/2026-05-06-aseprite-mcp-integration.md — entire file uses E:\Jaco\... paths, PowerShell commands (Get-Content, New-Item, Test-Path), and .exe references. This plan is not actionable outside the author's machine.	Low (design doc, not code)
6	Orphaned feature-requests/ directory	Two new files feature-requests/qmd-doc-search.md and feature-requests/unity-mcp-integration.md — no command, skill, or workflow references them. They exist in the repo but nothing acts on them. Consider adding to a triage workflow or a TRIAGE board reference.	Low

---

Detailed Analysis of #1 (High Priority)

// opencode.json line 16
"aseprite": {
  "environment": {           // 👈 key name: "environment"
    "ASEPRITE_PATH": "{env:ASEPRITE_PATH}"
  }
},
"godot": {
  "env": {                   // 👈 key name: "env"
    "GODOT_PATH": "{env:GODOT_PATH}",
    "DEBUG": "{env:DEBUG}"
  }
}

OpenCode's MCP config spec uses env (not environment) for per-server environment variables. If environment is silently ignored, the Aseprite MCP server won't find the Aseprite binary. Pick one key name and use it consistently.

---

Suggestions

1. Standardize on env in opencode.json — change the aseprite key from "environment" to "env".

2. Replace Test-Path in art-generate/SKILL.md with a cross-platform equivalent (e.g., test -f or a Node.js fs check).

3. Add behavioral specs for the 5 new skills in catalog.yaml at CCGS Skill Testing Framework/skills/utility/ (or their correct category).

4. Add config.yml at .github/ISSUE_TEMPLATE/config.yml to restore blank-issue/contact-link controls.

5. Create a TRIAGE label or workflow for feature-requests/ — or document that these are aspirational ideas, not committed work.

---

Summary

The PR is well-structured and the previously flagged issues were already fixed before merge. The current risks are: inconsistent MCP env var key (could break Aseprite MCP), missing config.yml, untested new skills, and a PowerShell-ism in a cross-platform skill file. None are blockers, but #1 should be fixed before release.

opencode session  |  github run

[github-actions]

Review: release v0.6.0 — Aseprite MCP Workflow

---

Quick Assessment

The PR is well-scoped and most issues flagged in prior CI reviews were already addressed in the committed code (portable env vars, test timeout, submodule CI init, bug-report.md moved correctly). I found 5 remaining issues, one of which is a real gap.

---

Issues

#	Issue	File	Severity
1	config.yml deleted without replacement	.github/workflows/ISSUE_TEMPLATE/config.yml removed (-8 lines), but no config.yml was created at .github/ISSUE_TEMPLATE/config.yml. GitHub will lose contact-links / blank-issue configuration.	Medium
2	PowerShell Test-Path in skill instructions	.opencode/skills/art-generate/SKILL.md:182 — Test-Path "assets/sprites/..." is Windows-only. Won't execute on Linux/macOS CI or agent sessions.	Medium
3	5 new skills registered with empty specs	skill-testing-framework/catalog.yaml:789-842 — art-generate, explore, hybrid-prototype, automated-smoke-test, init-template all have spec: "". No behavioral test coverage.	Medium
4	Plan doc hardcoded to Windows	framework/docs/superpowers/plans/2026-05-06-aseprite-mcp-integration.md — all commands use E:\Jaco\..., PowerShell, .exe. Future readers on macOS/Linux can't follow it.	Low (design doc)
5	Orphaned feature-requests/ directory	feature-requests/qmd-doc-search.md, feature-requests/unity-mcp-integration.md — nothing references them. No triage workflow, no command, no tracking.	Low

Non-issues (previously flagged, already fixed)

• environment vs env: Both MCP entries use "environment" — they are consistent. The second CI review was incorrect on this.
• Hardcoded Windows paths: Uses {env:ASEPRITE_PATH} — portable.
• --no-sync: Not present in committed code.
• Test runner timeout: Has SUITE_TIMEOUT=30000 with proper kill logic.
• bug-report.md: Successfully moved to .github/ISSUE_TEMPLATE/bug-report.md — content intact.
• Submodule CI: actions/checkout@v4 with submodules: recursive handles it.
• Help skill context: Static text, not shell execution — correct.

---

Recommendations

1. Add config.yml at .github/ISSUE_TEMPLATE/config.yml to restore blank-issue and contact-link controls that were lost when the old file was deleted.
2. Replace Test-Path in art-generate/SKILL.md:182 with a cross-platform equivalent (test -f path or generic file-existence check in the skill instructions).
3. Add behavioral specs for the 5 new skills in skill-testing-framework/catalog.yaml so they get test coverage.
4. Either remove orphaned feature-requests/ docs or add them to a tracking workflow so they don't become dead weight.

Verdict: Code quality is solid. The config.yml gap is the only issue that materially affects project behavior.

opencode session  |  github run