Total 50,394 skills, Code Quality has 2287 skills
Showing 12 of 2287 skills
Review a GitHub Pull Request as a responsible project owner using the `gh` CLI. Use when the user provides a PR URL (e.g. https://github.com/ORG/REPO/pull/N) or a PR number for the current git repo (prefer upstream, else origin) and wants an owner-grade review document `review-N.md` written in Chinese with copy-pastable GitHub comments in English. Scope the review to lines changed by the PR (do not nitpick unrelated pre-existing code), but apply best practices and flag any clear bugs, security issues, or CI failures caused by the change.
Manages the structured relationship between ScriptableObjects (Data) and Prefabs (Logic/Visuals) in Unity 6. Follows the 'SO-to-Mono' Bridge pattern to ensure instance independence (e.g., individual health for identical robots) while maintaining a clean, data-driven architecture. Use when: (1) Creating new unit/item types, (2) Wiring SO data to Prefab MonoBehaviours, (3) Resolving data-sharing bugs where changing one SO affects all instances.
Use when writing code, documentation, or comments - always use accessible and respectful terminology
Invoke IMMEDIATELY via python script when user requests refactoring analysis, technical debt review, or code quality improvement. Do NOT explore first - the script orchestrates exploration.
Phase 3 of disciplined development. Executes approved implementation plans step by step. Each step includes tests, follows the design exactly, and produces reviewable commits.
Puts Claude code into a different frame of mind for better results
Audit repos for architectural drift, dead code, and abstraction bloat.
Analyze codebase for GoF design patterns - detection, suggestions, evaluation with stack-aware adaptations
Review code changes for quality, correctness, and best practices. Use when asked to review a PR, review changes, or assess code quality before merge.
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Use when you need to check, verify, validate or understand code or structure of a file (often code related files or markdown) - automatically detects file type, finds appropriate LSP/linter in mise, and runs validation
Apply Pragmatic Programmer (Hunt & Thomas, 2019 edition) advice to software tasks and code reviews; use when the user asks to apply pragmatic tips, asks how to approach a task, or when performing a code review to map relevant chapters/tips to the current context.