Loading...
Loading...
Found 1,173 Skills
Generate context-aware quality checklists for code review and QA using IEEE 1028 base standards plus LLM contextual additions
Reviews Elixir code for performance issues including GenServer bottlenecks, memory usage, and concurrency patterns. Use when reviewing high-throughput code or investigating performance issues.
Suggests clear, descriptive names for functions and variables following consistent naming conventions. Use when naming new code constructs, renaming for clarity, or reviewing naming in code reviews.
Use when user asks to leverage claude or claude code to do something (e.g. implement a feature design or review codes, etc). Provides non-interactive automation mode for hands-off task execution without approval prompts.
This skill should be used when the user asks to "use the oracle" or "ask the oracle" for deep research, analysis, or architectural questions. The oracle excels at multi-source research combining codebase exploration and web searches, then synthesizing findings into actionable answers. Use for complex questions requiring investigation across multiple sources, architectural analysis, refactoring plans, debugging mysteries, and code reviews.
Use when executing implementation plans with independent tasks in the current session
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
Use Slopwatch to detect LLM reward hacking in .NET code changes. Run after every code modification to catch disabled tests, suppressed warnings, empty catch blocks, and other shortcuts that mask real problems.
Security auditing for Rust/WebAssembly applications. Identifies vulnerabilities, reviews unsafe code, validates input handling, and ensures secure defaults. Follows OWASP guidelines and Rust security best practices.
Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
Use when dispatching code reviews for tiers with N greater than 1 (max-20x, max-5x) in subagent-driven development, or manually for critical changes over 200 lines or security-sensitive code
Workflow for executing implementation tasks. Use this skill when you need to: (1) Execute a prepared implementation plan (2) Implement tasks sequentially based on dependency resolution (3) For each task: implement → verify → self-review → external review This skill enforces: (a) dependency-based task execution, (b) per-task review cycle.