doc-tidy
25Skill Claude CodeCodex
Scan the repo for scattered documentation files, analyze organization issues, and output cleanup recommendations. Analysis only — no changes made.
Skill Claude CodeCodex
Scan the repo for scattered documentation files, analyze organization issues, and output cleanup recommendations. Analysis only — no changes made.
Skill Claude CodeCodex
Smart implementation — read a plan, execute step by step with auto-compilation, subagent dispatch for large tasks, and checkpoint-based resume.
Skill Claude CodeCodex
Explain the architecture and logic of a specified module or design in plain, approachable language.
Skill Claude CodeCodex
Composite command: run /qq:brief and /qq:timeline in parallel, generating a complete PR review package.
Skill Claude CodeCodex
Entry point — detect where you are in the dev workflow and guide you to the right next step.
Skill Claude CodeCodex
Explain technical concepts using everyday analogies that a grandma or 5-year-old could understand.
Skill Claude CodeCodex
Generate a technical implementation plan from a game design document or a brief description. Outputs architecture, interfaces, ordered steps with file paths.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Review changes from the most recent interaction (skills, configs, settings, and other lightweight changes) for quality and consistency.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Run Unity unit/integration tests and check for runtime errors.
Skill Claude CodeCodex
Group the current branch's commit history into semantic phases along a timeline, and generate two review documents: architecture evolution + code review.