Loading...
Loading...
Found 1,232 Skills
Use this skill when the user asks for a review, audit, evaluation or analysis of a codebase, to identify bugs, security vulnerabilities, performance bottlenecks, or code quality concerns.
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
Adaptive test-driven development cycle. Detects harness capabilities and routes to guided (manual phase control) or automated (orchestrated) mode. Invoke with /tdd for automated or /tdd red|domain|green|commit for guided.
Generate JSDoc/docstrings for functions
Structured code review approach covering security, quality, performance, and consistency.
Prepare branch for code review by building context, identifying issues, and suggesting improvements
Review changes for test gaps, simplification, naming consistency, reuse opportunities, and TODO quality
Lead Software Engineer. Use this skill whenever the user mentions coding, debugging, refactoring, or implementation, even if they don't explicitly ask for an "engineer." Use it to translate technical blueprints into clean code.
Use when verifying code works — after feature work, before committing, before deploy, or any request to "verify", "check", or "make sure it works"
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm
Analyzes Rails code quality, architecture, and patterns without modifying code. Use when the user wants a code review, quality analysis, architecture audit, or when user mentions review, audit, code quality, anti-patterns, or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist agents), writing new tests (use rspec-agent), or generating new features.
Run Codex, Claude Code, and Gemini CLI reviews against the current branch concurrently, deduplicate the findings, and report only the review comments that are still valid for the current codebase.