tykisgod

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.

Analyze .asmdef dependency relationships — Mermaid graph + dependency matrix + issue detection.

Batch commit all uncommitted changes and push to the remote repository.

Summarize all changes Claude Code made during this conversation.

Review changes from the most recent interaction (skills, configs, settings, and other lightweight changes) for quality and consistency.

Generate a technical implementation plan from a game design document or a brief description. Outputs architecture, interfaces, ordered steps with file paths.

Run Unity unit/integration tests and check for runtime errors.

Explain the architecture and logic of a specified module or design in plain, approachable language.

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.

Composite command: run /qq:brief and /qq:timeline in parallel, generating a complete PR review package.

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.

Scan the repo for scattered documentation files, analyze organization issues, and output cleanup recommendations. Analysis only — no changes made.