Loading...
Loading...
Found 1,193 Skills
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.
Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, and Stylelint. Use when you need the exact rule name or config for a specific linter, not for running a linter.
Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.
Reviews pull requests and code diffs for concrete bugs and CLAUDE.md compliance. Use when asked to review a PR, branch diff, or pre-merge changes. Reports only high-confidence, actionable issues.
Query efficiency audit worker (L3). Checks redundant entity fetches, N-UPDATE/DELETE loops, unnecessary resolves, over-fetching, missing bulk operations, wrong caching scope. Returns findings with severity, location, effort, recommendations.
Coordinates linters, pre-commit hooks, and test infrastructure setup
Technical solution evaluation and code review in the style of Linus Torvalds. Only use this when the user explicitly requests a Linus-style review or explicitly asks for a rigorous evaluation of code changes/technical solutions (e.g., "review changes/code", "evaluate if the solution is appropriate", "check submission standards", "linus-tech-review").
Analyzes codebases to generate comprehensive documentation including structure, languages, frameworks, dependencies, design patterns, and technical debt. Use when user says "analyze repository", "understand codebase", "document project", or when exploring unfamiliar code.
Use when working on Solana Anchor programs, including Rust program files, TypeScript tests, and Anchor.toml configuration. Enforces coding guidelines like proper variable naming, avoiding magic numbers, using Array<T> syntax, and Anchor 0.32.1 best practices.
Coordinates 9 specialized audit workers (security, build, architecture, code quality, dependencies, dead code, observability, concurrency, lifecycle). Researches best practices, delegates parallel audits, aggregates results into single Linear task in Epic 0.
Codebase analysis tool for quality-first editing. Scan before edit to understand relationships, patterns, and impact.
Expert in TypeScript development with best practices for type safety and clean code