Loading...
Loading...
Found 955 Skills
Review an existing game codebase for architecture, performance, and best practices
Local code review tool for self-inspection before git push. Triggered when users request phrases like "review my code", "check code changes", "review this commit", "review this", "code review", "git review", "help me check my code". Supports reviewing unstaged, staged uncommitted, and committed unpushed changes, and outputs a Markdown review report with scores.
Manage global ignore patterns for lint-relative-paths. TRIGGERS - statusline ignore, add ignore pattern, lint ignore, path lint exclude.
Systematic code refactoring following Martin Fowler's catalog. Methodologies: characterization tests, Red-Green-Refactor, incremental transformation. Capabilities: SOLID compliance, DRY cleanup, code smell detection, complexity reduction, legacy modernization, design patterns, functional programming patterns. Actions: refactor, extract, inline, rename, move, simplify code. Keywords: refactor, SOLID, DRY, code smell, complexity, extract method, inline, rename, move, clean code, technical debt, legacy code, design pattern, characterization test, Red-Green-Refactor, functional programming, higher-order function, immutability, pure function, composition, currying, side effects. Use when: improving code quality, reducing technical debt, applying SOLID principles, fixing DRY violations, removing code smells, modernizing legacy code, applying design patterns.
This skill should be used when the user asks to "remove AI slop", "clean up AI code", "remove AI patterns", "fix AI-generated code", "clean up PR", "remove unnecessary comments", "fix defensive checks", or mentions AI slop, AI code cleanup, or code quality issues from AI-assisted development. Identifies and removes unnecessary comments, defensive checks, type casts to any, and style inconsistencies.
When writing or reviewing code to eliminate duplicated knowledge and business logic. Use when the user says "this is duplicated," "we have this in two places," "single source of truth," "DRY this up," or "shotgun surgery." For premature abstraction concerns, see yagni.
AQE skill
Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check(). Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback. Covers documentation requirements, DESCRIPTION field standards, URL validation, examples, and administrative requirements.
Multi-agent quality improvement review with constructive feedback. Provides suggestions for best practices, code quality, alternatives, and performance optimization.
Comprehensive skill for 89 refactoring techniques and code smells with PHP 8.3+ examples. Covers composing methods, moving features, organizing data, simplifying conditionals, simplifying method calls, dealing with generalization, and detecting 22 code smells across bloaters, OO abusers, change preventers, dispensables, and couplers.
Run a structured, adversarial multi-agent bug review pipeline on a codebase. Use this skill whenever the user wants to find bugs, audit code quality, review a codebase for issues, or run any kind of bug-finding or code analysis workflow. Also trigger when the user asks to 'review my code for bugs', 'find all issues in this repo', 'audit this codebase', or any similar request. The pipeline uses three sequential phases: a Bug Finder that maximizes issue discovery, a Bug Adversary that challenges false positives, and an Arbiter that issues final verdicts — producing a clean, high-confidence bug report.
Checks session scope mismatch, streaming resource holding, missing cleanup, pool config, error path leaks, factory vs injection anti-patterns.