All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,946
- 623
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 14,617–14,640 of 14,946 skills
- Flow Next Plan ReviewCarmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow specs or design docs. Triggers on /flow-next:plan-review.Votes: 0GitHub stars: 704
- Flow Next Impl ReviewJohn Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.Votes: 0GitHub stars: 704
- Protein QcQuality control metrics and filtering thresholds for protein design. Use this skill when: (1) Evaluating design quality for binding, expression, or structure, (2) Setting filtering thresholds for pLDDT, ipTM, PAE, (3) Checking sequence liabilities (cysteines, deamidation, polybasic clusters), (4) Creating multi-stage filtering pipelines, (5) Computing PyRosetta interface metrics (dG, SC, dSASA), (6) Checking biophysical properties (instability, GRAVY, pI), (7) Ranking designs with composite s...Votes: 0GitHub stars: 157
- Simple SkillA simple and safe skill for code reviewVotes: 0GitHub stars: 25
- CleanA safe skill that helps with code review tasksVotes: 0GitHub stars: 25
- Specstory YakAnalyze your SpecStory AI coding sessions in .specstory/history for yak shaving - when your initial goal got derailed into rabbit holes. Run when user says "analyze my yak shaving", "check for rabbit holes", "how distracted was I", or "yak shave score".Votes: 0GitHub stars: 35
- Clay Common ErrorsDiagnose and fix Clay common errors and exceptions. Use when encountering Clay errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "clay error", "fix clay", "clay not working", "debug clay".Votes: 0GitHub stars: 2,688
- Clay Advanced TroubleshootingApply Clay advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Clay support escalation. Trigger with phrases like "clay hard bug", "clay mystery error", "clay impossible to debug", "difficult clay issue", "clay deep debug".Votes: 0GitHub stars: 2,688
- Apollo Common ErrorsDiagnose and fix common Apollo.io API errors. Use when encountering Apollo API errors, debugging integration issues, or troubleshooting failed requests. Trigger with phrases like "apollo error", "apollo api error", "debug apollo", "apollo 401", "apollo 429", "apollo troubleshoot".Votes: 0GitHub stars: 2,688
- Overnight DevelopmentAutomates software development overnight using git hooks to enforce test-driven Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.Votes: 0GitHub stars: 2,688
- Detecting Memory LeaksDetect potential memory leaks and analyze memory usage patterns in code. Use when troubleshooting performance issues related to memory growth or identifying leak sources. Trigger with phrases like "detect memory leaks", "analyze memory usage", or "find memory issues".Votes: 0GitHub stars: 2,688
- Analyzing LogsAnalyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".Votes: 0GitHub stars: 2,688
- Detecting Performance BottlenecksExecute this skill enables AI assistant to detect and resolve performance bottlenecks in applications. it analyzes cpu, memory, i/o, and database performance to identify areas of concern. use this skill when you need to diagnose slow application performance, op... Use when optimizing performance. Trigger with phrases like 'optimize', 'performance', or 'speed up'.Votes: 0GitHub stars: 2,688
- Generating Smart CommitsExecute use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.Votes: 0GitHub stars: 2,688
- Debug Cuda CrashTutorial for debugging CUDA crashes using API loggingVotes: 0GitHub stars: 416
- Managing Project RulesCreates and updates modular project rules for Claude Code in .claude/rules/ directory. Use when creating, updating, or modifying rule files, organizing project guidelines, setting up code standards, or when user mentions "create rules", "update rules", "add rules", or "rule configuration".Votes: 0GitHub stars: 416
- Implementation ReviewAutomatically trigger review agents after task completion. Use when strategic-planner finishes planning tasks (calls plan-consultant) or when main agent completes coding tasks in /implement workflow (calls code-reviewer). Triggers on phrases like "plan complete", "implementation done", "coding finished", "ready for review".Votes: 0GitHub stars: 416
- Thiserror ExpertProvides guidance on creating custom error types with thiserror, including proper derive macros, error messages, and source error chaining. Activates when users define error enums or work with thiserror.Votes: 0GitHub stars: 416
- Let Chains AdvisorIdentifies deeply nested if-let expressions and suggests let chains for cleaner control flow. Activates when users write nested conditionals with pattern matching.Votes: 0GitHub stars: 416
- Hexagonal AdvisorReviews code architecture for hexagonal patterns, checks dependency directions, and suggests improvements for ports and adapters separation. Activates when users work with services, repositories, or architectural patterns.Votes: 0GitHub stars: 416
- Error Handler AdvisorProactively reviews error handling patterns and suggests improvements using Result types, proper error propagation, and idiomatic patterns. Activates when users write error handling code or use unwrap/expect.Votes: 0GitHub stars: 416
- Dev Tools SkillUse when the user says "use the DevTools skill" or when they need help debugging a web app with Chrome DevTools MCP (UI bugs, incorrect behavior, console errors, network/API failures, or performance/lag), especially if the user seems inexperienced and needs guided, step-by-step diagnosis.Votes: 0GitHub stars: 416
- Root Cause TracingUse when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behaviorVotes: 0GitHub stars: 416
- Typescript StrictEnforce TypeScript strict mode and type safety. Use when setting up projects, reviewing code, or when type errors are ignored. Covers strict flags, no-any rules, and type inference best practices.Votes: 0GitHub stars: 416