Loading...
Loading...
Found 1,194 Skills
AST-based semantic code search skill for AI agents. Teaches agents to use sqry's 34 MCP tools for finding symbols by structure (functions, classes, types), tracing relationships (callers, callees, imports, inheritance), analyzing dependencies, and detecting code quality issues. Unlike embedding-based search, sqry parses code like a compiler. Supports 37 languages. Uses tiered discovery: start with Quick Tool Selection below, load reference files only when you need parameter details or advanced workflows.
Review code changes against STYLE_GUIDE.md before committing or creating PRs. Catches naming violations, import ordering issues, anti-pattern reintroduction, and convention drift. Run after /setup-ai or /generate-comprehensive-style-guide has created a style guide.
Catalogue of preferred linter rules, TypeScript flags, and architectural boundary checks for making bug classes and design drift mechanically impossible. Use when setting up linting in a new project, hardening an existing project, responding to a class of bug by encoding a rule, or deciding which linter to reach for on a given stack. Pairs with the `hk` skill which handles wiring hooks.
Iterative code refinement through plan → code → evaluate → refine cycles. Runs lint checks (ruff), tests (pytest), and structured self-evaluation each cycle, then diagnoses failures and refines. Decomposes complex tasks into sequential phases, iterates up to 3 times per phase (10 total). Use when: the main agent delegates a code task with 'MODE: MORE_EFFORT', the user selects 'More Effort' code generation mode, or the task explicitly requests iterative refinement for higher code quality. Do NOT use for single-pass code generation (Lite mode), experiment pipeline orchestration (use experiment-pipeline), or diagnosing a specific experiment failure (use experiment-craft).
Comprehensive Go backend code review with optional parallel agents
Use when restructuring existing code without changing observable behavior, especially when a feature or bug fix is hard because the current design is awkward, duplicated, confusing, or risky to modify.
Review changed code for reuse, quality, and efficiency, then fix any issues found.
Comprehensive pull request review using specialized agents
Vue2 Frontend Code Review Assistant. Reviews code changes in the src directory of Vue2 projects. Covers 9 major dimensions: component specifications, code style, naming, logic, network requests, computed, security, best practices, and absolute prohibitions. Trigger scenarios: pre-merge review, pre-commit quality check, Code Review for Vue2 code.
Organize functions in a file or across a branch.
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.
Use when the user asks to review code, review changes, review a commit, review a PR, audit code quality, check for security issues, or generate a code review report. Trigger on phrases like "review my changes", "코드 리뷰", "check my code", "review the last commit", "what do you think of this diff", "compare branches", "code audit" — even if they don't say "code review" explicitly. For persistent file output use `code-review-md` (markdown) or `code-review-html` (markdown + HTML).