Claude Skills by tykisgod

github.com/tykisgod

27 skillsA× 270 installs72 views

Add TestsAAuthor Unity EditMode, PlayMode, or regression tests for the current change without conflating that with test execution.developmentbashexpressVotes: 0GitHub stars: 11
Best PracticeAQuick Unity best-practice check — run after editing C# files to catch anti-patterns, performance issues, and runtime safety problems.developmentc#bashVotes: 0GitHub stars: 11
BootstrapADecompose 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.developmentgobashVotes: 0GitHub stars: 11
BriefACompare the current branch against its base branch and generate two review documents: architecture change diagram + PR review checklist.developmentc#nodeVotes: 0GitHub stars: 11
ChangesASummarize all changes Claude Code made during this conversation.developmentbashgitVotes: 0GitHub stars: 11
Claude Code ReviewADeep code review via a separate Claude CLI run — reviews uncommitted changes by default, loops until no critical issues remain. Use after implementation (e.g. /qq:execute), before /qq:test and /qq:commit-push.developmentgobashVotes: 0GitHub stars: 11
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Claude Plan ReviewASend a design document to a separate Claude CLI run for review, then revise the document based on findings. Automatically loops until no critical issues remain or 5 rounds are complete.developmentgobashVotes: 0GitHub stars: 11
Codex Code ReviewACross-model code review via Codex CLI — reviews uncommitted changes by default, loops until no critical issues remain. Use after implementation (e.g. /qq:execute), before /qq:test and /qq:commit-push.developmentgobashVotes: 0GitHub stars: 11
Codex Plan ReviewASend 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.developmentgobashVotes: 0GitHub stars: 11
Commit PushABatch commit all uncommitted changes (or only the given files) and push to the remote repository.developmentgobashVotes: 0GitHub stars: 11
DepsAAnalyze .asmdef dependency relationships — Mermaid graph + dependency matrix + issue detection.developmentVotes: 0GitHub stars: 11
Design ResearchASearch 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.developmentgogitVotes: 0GitHub stars: 11
DesignAWrite 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.developmentgobashVotes: 0GitHub stars: 11
Doc DriftACompare design documents against actual code/config, find inconsistencies, and output a prioritized attention list.developmentgodocumentationVotes: 0GitHub stars: 11
Doc TidyAScan the repo for scattered documentation files, analyze organization issues, and output cleanup recommendations. Analysis only — no changes made.developmentgogitVotes: 0GitHub stars: 11
ExecuteASmart implementation — read a plan, execute step by step with auto-compilation, subagent dispatch for large tasks, and checkpoint-based resume.developmentgobashVotes: 0GitHub stars: 11
ExplainAExplain the architecture and logic of a specified module or design in plain, approachable language.developmentdocumentationVotes: 0GitHub stars: 11
Full BriefAComposite command: run /qq:brief and /qq:timeline in parallel, generating a complete PR review package.developmentgoVotes: 0GitHub stars: 11
GoAEntry point — detect where you are in the dev workflow and guide you to the right next step.developmentgobashVotes: 0GitHub stars: 11
GrandmaAExplain technical concepts using everyday analogies that a grandma or 5-year-old could understand.developmentgoVotes: 0GitHub stars: 11
PlanAGenerate a technical implementation plan from a game design document or a brief description. Outputs architecture, interfaces, ordered steps with file paths.developmentgobashVotes: 0GitHub stars: 11
Post Design ReviewAReview 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.developmentVotes: 0GitHub stars: 11
Self ReviewAReview changes from the most recent interaction (skills, configs, settings, and other lightweight changes) for quality and consistency.developmentbashVotes: 0GitHub stars: 11
Tech ResearchASearch 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.developmentgitVotes: 0GitHub stars: 11
TestARun Unity unit/integration tests and check for runtime errors.developmentrustgoVotes: 0GitHub stars: 11
TimelineAGroup the current branch's commit history into semantic phases along a timeline, and generate two review documents: architecture evolution + code review.developmentgoc#Votes: 0GitHub stars: 11
Doc SyncALocal 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.developmentpythongoVotes: 0GitHub stars: 11