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,593–14,616 of 14,946 skills
- Claude ReviewReview code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.Votes: 0GitHub stars: 666
- Claude FrameworkCLAUDE Framework coding standards for code quality, naming conventions, error handling, security, testing, database, and loggingVotes: 0GitHub stars: 666
- Claude Codex Guardrail LoopUse after planning or implementing non-trivial tasks - runs Codex MCP background verification/review for quality gates (plan validation + implementation review)Votes: 0GitHub stars: 666
- Call GeminiInvoke the Gemini CLI for architecture and scalability review.Votes: 0GitHub stars: 666
- Evernote Debug BundleDebug Evernote API issues with diagnostic tools and techniques. Use when troubleshooting API calls, inspecting requests/responses, or diagnosing integration problems. Trigger with phrases like "debug evernote", "evernote diagnostic", "troubleshoot evernote", "evernote logs", "inspect evernote".Votes: 0GitHub stars: 2,688
- Evernote Common ErrorsDiagnose and fix common Evernote API errors. Use when encountering Evernote API exceptions, debugging failures, or troubleshooting integration issues. Trigger with phrases like "evernote error", "evernote exception", "fix evernote issue", "debug evernote", "evernote troubleshooting".Votes: 0GitHub stars: 2,688
- Documenso Debug BundleComprehensive debugging toolkit for Documenso integrations. Use when troubleshooting complex issues, gathering diagnostic information, or creating support tickets for Documenso problems. Trigger with phrases like "debug documenso", "documenso diagnostics", "troubleshoot documenso", "documenso support ticket".Votes: 0GitHub stars: 2,688
- Documenso Common ErrorsDiagnose and resolve common Documenso API errors and issues. Use when encountering Documenso errors, debugging integration issues, or troubleshooting failed operations. Trigger with phrases like "documenso error", "documenso 401", "documenso failed", "fix documenso", "documenso not working".Votes: 0GitHub stars: 2,688
- Deepgram Sdk PatternsApply production-ready Deepgram SDK patterns for TypeScript and Python. Use when implementing Deepgram integrations, refactoring SDK usage, or establishing team coding standards for Deepgram. Trigger with phrases like "deepgram SDK patterns", "deepgram best practices", "deepgram code patterns", "idiomatic deepgram", "deepgram typescript".Votes: 0GitHub stars: 2,688
- Deepgram Common ErrorsDiagnose and fix common Deepgram errors and issues. Use when troubleshooting Deepgram API errors, debugging transcription failures, or resolving integration issues. Trigger with phrases like "deepgram error", "deepgram not working", "fix deepgram", "deepgram troubleshoot", "transcription failed".Votes: 0GitHub stars: 2,688
- Databricks Common ErrorsDiagnose and fix Databricks common errors and exceptions. Use when encountering Databricks errors, debugging failed jobs, or troubleshooting cluster and notebook issues. Trigger with phrases like "databricks error", "fix databricks", "databricks not working", "debug databricks", "spark error".Votes: 0GitHub stars: 2,688
- Customerio Known PitfallsIdentify and avoid Customer.io anti-patterns. Use when reviewing integrations, avoiding common mistakes, or optimizing existing Customer.io implementations. Trigger with phrases like "customer.io mistakes", "customer.io anti-patterns", "customer.io best practices", "customer.io gotchas".Votes: 0GitHub stars: 2,688
- Quality ReviewerDeep code review with web research to verify against latest ecosystem. Use when user says 'double check against latest', 'verify versions', 'check security', 'review against docs', or needs deep analysis beyond automatic quality hook.Votes: 0GitHub stars: 416
- Lint TypecheckRun ESLint and TypeScript type checking on the frontend codebase. Use when user mentions "lint", "type check", "check code", "eslint", "tsc", or before committing changes.Votes: 0GitHub stars: 416
- AnalyzerComprehensive codebase analysis methodology for existing projects. Use when onboarding to a new codebase, doing periodic health checks, or before refactoring.Votes: 0GitHub stars: 666
- Analyze CodebaseAnalyze a codebase to generate a comprehensive architecture and structure report. Use when user wants to understand a codebase, explore project structure, or generate analysis.Votes: 0GitHub stars: 666
- Slop DetectorDetects AI-generated writing patterns in prose. Use when reviewing docs for slop, vague language, or identity leaks before publishing.Votes: 0GitHub stars: 342
- Response CompressionCompresses verbose responses by removing filler and framing to save 200-400 tokens. Use when responses feel bloated or context is filling fast.Votes: 0GitHub stars: 342
- Validate AlbumValidates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.Votes: 0GitHub stars: 497
- 2 Identify Ioku24 AutorankrIdentify friction points, bottlenecks, bugs, and technical debt. Use for audits, debugging sessions, when something feels wrong, or before major work to surface hidden issues. This is the second system in the 5-system framework.Votes: 0GitHub stars: 666
- Explicit CheckerScans lyrics for explicit content and verifies that explicit flags match actual content. Use before Suno generation or release to ensure accurate content ratings.Votes: 0GitHub stars: 497
- Debug WorkflowExecute the Debug Code Change workflow end-to-end with safety gates. Use when debugging code changes, investigating issues, or performing root cause analysis with audit trail.Votes: 0GitHub stars: 4
- CritiqueFind failure modes, edge cases, ambiguities, and exploit paths in plans, code, or designs. Use when reviewing proposals, auditing security, stress-testing logic, or validating assumptions.Votes: 0GitHub stars: 4
- Flow Next PrimeComprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.Votes: 0GitHub stars: 704