Search Results for "code review"
code-review-medium
★ 2.0kStandard code review for medium PRs (100-500 lines). Includes code quality, security basics, and test coverage analysis.
code-review
★ 2.0kAnalyze PR diffs and generate review comments from code quality, security, and performance perspectives. Use for code reviews, quality checks, and security analysis.
code-review-small
★ 2.0kQuick code review for small PRs (<100 lines). Focuses on basic code quality, naming conventions, and obvious bugs.
code-review
★ 1.1kUse when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
exa-known-pitfalls
★ 939Identify and avoid Exa anti-patterns and common integration mistakes.Use when reviewing Exa code for issues, onboarding new developers,or auditing existing Exa integrations for best practices violations.Trigger with phrases like "exa mistakes", "exa anti-patterns","exa pitfalls", "exa what not to do", "exa code review".
retellai-known-pitfalls
★ 939Identify and avoid Retell AI anti-patterns and common integration mistakes.Use when reviewing Retell AI code for issues, onboarding new developers,or auditing existing Retell AI integrations for best practices violations.Trigger with phrases like "retellai mistakes", "retellai anti-patterns","retellai pitfalls", "retellai what not to do", "retellai code review".
perplexity-known-pitfalls
★ 939Identify and avoid Perplexity anti-patterns and common integration mistakes.Use when reviewing Perplexity code for issues, onboarding new developers,or auditing existing Perplexity integrations for best practices violations.Trigger with phrases like "perplexity mistakes", "perplexity anti-patterns","perplexity pitfalls", "perplexity what not to do", "perplexity code review".
firecrawl-known-pitfalls
★ 939Identify and avoid FireCrawl anti-patterns and common integration mistakes.Use when reviewing FireCrawl code for issues, onboarding new developers,or auditing existing FireCrawl integrations for best practices violations.Trigger with phrases like "firecrawl mistakes", "firecrawl anti-patterns","firecrawl pitfalls", "firecrawl what not to do", "firecrawl code review".
clay-known-pitfalls
★ 920Identify and avoid Clay anti-patterns and common integration mistakes.Use when reviewing Clay code for issues, onboarding new developers,or auditing existing Clay integrations for best practices violations.Trigger with phrases like "clay mistakes", "clay anti-patterns","clay pitfalls", "clay what not to do", "clay code review".
replit-known-pitfalls
★ 920Identify and avoid Replit anti-patterns and common integration mistakes.Use when reviewing Replit code for issues, onboarding new developers,or auditing existing Replit integrations for best practices violations.Trigger with phrases like "replit mistakes", "replit anti-patterns","replit pitfalls", "replit what not to do", "replit code review".
windsurf-known-pitfalls
★ 920Identify and avoid Windsurf anti-patterns and common integration mistakes.Use when reviewing Windsurf code for issues, onboarding new developers,or auditing existing Windsurf integrations for best practices violations.Trigger with phrases like "windsurf mistakes", "windsurf anti-patterns","windsurf pitfalls", "windsurf what not to do", "windsurf code review".
supabase-known-pitfalls
★ 878Identify and avoid Supabase anti-patterns and common integration mistakes.Use when reviewing Supabase code for issues, onboarding new developers,or auditing existing Supabase integrations for best practices violations.Trigger with phrases like "supabase mistakes", "supabase anti-patterns","supabase pitfalls", "supabase what not to do", "supabase code review".
vercel-known-pitfalls
★ 878Identify and avoid Vercel anti-patterns and common integration mistakes.Use when reviewing Vercel code for issues, onboarding new developers,or auditing existing Vercel integrations for best practices violations.Trigger with phrases like "vercel mistakes", "vercel anti-patterns","vercel pitfalls", "vercel what not to do", "vercel code review".
performance-optimization
★ 701Apply systematic performance optimization techniques for Python and Rust code: estimation + profiling, API/bulk design, algorithmic wins, cache-friendly memory layout, fewer allocations, fast paths, caching, and compiler-friendly hot loops. Use for performance code reviews, refactors, and profiling-driven optimizations. Keywords: performance, latency, throughput, cache, allocation, memory layout, PyO3, msgspec, tokio, async, pprof, py-spy, perf.
swiftui-performance-audit
★ 648Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
reviewing-changes
★ 460Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements. Use when reviewing pull requests, checking commits, analyzing code changes, verifying Bitwarden coding standards, evaluating unidirectional data flow pattern, checking services container dependency injection usage, reviewing security implementations, or assessing test coverage. Automatically invoked by CI pipeline or manually for interactive code reviews.
code-review
★ 327Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.
swiftui-performance-audit
★ 283Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Frequently Asked Questions
What is a Claude Skill?
It is a modular, protocol-based instruction set that enables Claude to perform specific tasks autonomously and efficiently.
How is this different from regular prompts?
Skills use the official Anthropic protocol for better token efficiency and automatic triggering compared to static prompts.
Does it support the new Claude Code CLI?
Yes, we provide specialized one-click installation commands designed specifically for Claude Code and OpenCode.
Can I use these skills in Cursor?
Absolutely, our library is fully compatible with popular IDEs and extensions including Cursor, Codex, and AntiGravity.
Are the skills on the website free to use?
Most skills in our 90,000+ database are free and open-source for the community to download and deploy.
How can I contribute my own skills?
Developers can easily share their work by submitting their own skill repositories through our community portal.