Loading...
Loading...
Found 920 Skills
Run Python quality checks with ruff, pytest, mypy, and bandit in deterministic order. Use WHEN user requests "quality gate", "lint", "verify code quality", "check python", or "pre-commit check". Use for pre-merge validation, CI/CD gating, or comprehensive code quality reports. Do NOT use for single-tool runs (run tool directly), debugging runtime bugs (use systematic-debugging), refactoring (use systematic-refactoring), or architecture review.
Fresh-subagent-per-task execution with two-stage review (ADR compliance + code quality). Use when an implementation plan exists with mostly independent tasks and you want quality gates between each. Use for "execute plan", "subagent", "dispatch tasks", or multi-task implementation runs. Do NOT use for single simple tasks, tightly coupled work needing shared context, or when the user wants manual review after each task.
Run Python (ruff) and JavaScript (Biome) linting, formatting, and code quality checks with auto-fix support. Use when code needs linting, formatting, or style checking before commits. Use for "lint", "format", "ruff", "biome", "code style", or "check quality". Do NOT use for comprehensive code review (use systematic-code-review).
Human reviewer self-review for backend PRs — naming, complexity, DB schema, test design, type precision. Use when user says "review my PR", "check my PR", "human review", or wants design/readability feedback. Applies to any TypeScript backend; pair with pr-review-frontend for full-stack PRs.
Agent skill for coder - invoke with $agent-coder
Guides idiomatic Lua 5.4 programming, module design, and project maintenance for Neovim plugin/config ecosystems (LazyVim, lazy.nvim) and macOS bar tools (SketchyBar/SbarLua). Covers style, tooling (StyLua, Selene, LuaLS), module patterns, and testing. Use when writing Lua code, configuring Neovim plugins, working with SketchyBar Lua configs, debugging Lua require/module errors, or when the user mentions Lua, .lua files, LazyVim, lazy.nvim, SbarLua, SketchyBar, luarocks, LuaLS, StyLua, or Selene.
Run Gemini CLI review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
Guide for writing inline comments and JSDoc in the codebase. Use when generating code for bug fixes, new components, refactoring, or feature implementation.
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
Multi-agent QA review team for code changes. This skill should be used when the user asks to "review my code", "run QA", "qa-team", "review this branch", "code review", "check my changes", or wants a comprehensive multi-perspective code review of the current branch's changes. Spawns parallel specialist agents (security, database, reliability, compatibility, data integrity, performance, frontend, copy) that independently review the diff and produce a converged report. Also includes two generalist reviewers for convergence validation.
Write tests before implementation code. Use when starting new features or fixing bugs. Covers Red-Green-Refactor cycle and TDD best practices.
Python code refactoring skills, covering code smell identification, design pattern application, readability improvement, and practical experience. This skill is applicable when users request "refactor code", "refactor", "code optimization", "improve code quality", "code smell review", "apply design patterns", "enhance readability", or submit code review requests. It supports generating structured refactoring documents after refactoring completion ("output refactoring document", "generate refactoring report"). It includes practical patterns extracted from 20+ real refactoring PRs in the vllm-ascend repository.