tykisgod
UserThe control plane for game-dev agents — close the loop with verified compile, test, and cross-model review across Unity, Godot, Unreal, and S&box. Lifecycle-aware /qq:go routing, 26 /qq:* slash commands. Claude Code-first, agent-agnostic via HTTP and MCP.
Categories
Indexed Skills (26)
add-tests
Author Unity EditMode, PlayMode, or regression tests for the current change without conflating that with test execution.
best-practice
Quick Unity best-practice check — run after editing C# files to catch anti-patterns, performance issues, and runtime safety problems.
bootstrap
Decompose a high-level game vision (pillars + rules + references) into executable epics, then orchestrate the full qq pipeline for each. Use when starting a new project, bootstrapping a prototype from a pitch, or breaking a large initiative into parallel workstreams.
brief
Compare the current branch against develop and generate two review documents: architecture change diagram + PR review checklist.
claude-code-review
Deep code review via Claude subagent — reviews uncommitted changes by default, loops until no critical issues remain. Use after /qq:test passes, before /qq:commit-push.
claude-plan-review
Send a design document to a Claude subagent for review, then revise the document based on findings. Automatically loops until no critical issues remain or 5 rounds are complete.
codex-code-review
Cross-model code review via Codex CLI — reviews uncommitted changes by default, loops until no critical issues remain. Use after /qq:test passes, before /qq:commit-push.
codex-plan-review
Send a design document to Codex CLI for review, then revise the document based on the findings. Automatically loops until no critical issues remain or 5 rounds are completed.
commit-push
Batch commit all uncommitted changes and push to the remote repository.
deps
Analyze .asmdef dependency relationships — Mermaid graph + dependency matrix + issue detection.
design
Write a game design document from a one-liner, rough draft, or feature discussion. Outputs a structured design doc ready for /qq:plan. Use when starting a new feature, fleshing out a game idea, or documenting a design before implementation.
doc-drift
Compare design documents against actual code/config, find inconsistencies, and output a prioritized attention list.
doc-sync
Local on-demand doc-sync: detect doc↔code drift, draft the reconciling updates (anchors + prose), present them as a reviewable diff, and land only what the human approves. Goes beyond qq:doc-drift's report-only by closing the loop — but never auto-commits and never touches code.
doc-tidy
Scan the repo for scattered documentation files, analyze organization issues, and output cleanup recommendations. Analysis only — no changes made.
execute
Smart implementation — read a plan, execute step by step with auto-compilation, subagent dispatch for large tasks, and checkpoint-based resume.
go
Entry point — detect where you are in the dev workflow and guide you to the right next step.
plan
Generate a technical implementation plan from a game design document or a brief description. Outputs architecture, interfaces, ordered steps with file paths.
self-review
Review changes from the most recent interaction (skills, configs, settings, and other lightweight changes) for quality and consistency.
timeline
Group the current branch's commit history into semantic phases along a timeline, and generate two review documents: architecture evolution + code review.
changes
Summarize all changes Claude Code made during this conversation.
design-research
Search for how other games solve a specific design problem — game loops, mechanics, systems, progression, economy. Returns a comparison of 2-4 reference games with what to borrow. Use when designing a new feature, exploring game mechanics, or looking for design inspiration before writing a design doc.
explain
Explain the architecture and logic of a specified module or design in plain, approachable language.
full-brief
Composite command: run /qq:brief and /qq:timeline in parallel, generating a complete PR review package.
grandma
Explain technical concepts using everyday analogies that a grandma or 5-year-old could understand.
post-design-review
Review a game design document from an implementer's perspective — check self-consistency, playability, buildability, and codebase gaps. Use after writing a design doc, or when you want to validate an existing design against the current codebase.
tech-research
Search GitHub, Stack Overflow, and technical blogs for solutions to a technical implementation problem. Returns a comparative analysis with a recommendation. Use when facing a technical decision, choosing a library, or looking for proven patterns in similar projects.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.