All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,950
- 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,809–14,832 of 14,950 skills
- When Reviewing Pull Request Orchestrate Comprehensive Code ReviewUse when conducting comprehensive code review for pull requests across multiple quality dimensions. Orchestrates 12-15 specialized reviewer agents across 4 phases using star topology coordination. Covers automated checks, parallel specialized reviews (quality, security, performance, architecture, documentation), integration analysis, and final merge recommendation in a 4-hour workflow.Votes: 0GitHub stars: 4
- Solid SwiftUse when applying SOLID principles to Swift 6/SwiftUI code — file-size limits, protocol separation, @Observable, actors, feature-modular architecture.Votes: 0GitHub stars: 29
- Solid DetectionUse when determining which language-specific SOLID skill to load, detecting project type from config files, or resolving interface directory conventions.Votes: 0GitHub stars: 29
- Solid ReactSOLID principles for React 19. Files < 100 lines, hooks separated, interfaces in src/interfaces/, JSDoc mandatory. Use for React architecture and code quality.Votes: 0GitHub stars: 29
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutionsVotes: 0GitHub stars: 37
- Solid NextjsThis skill should be used when the user asks about "SOLID principles", "Next.js architecture", "modular structure", "code organization", "file size limits", "interface separation", or "JSDoc documentation". Enforces files < 150 lines with mandatory JSDoc and separated interfaces.Votes: 0GitHub stars: 29
- Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceedingVotes: 0GitHub stars: 37
- Repo CleanupUse when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.Votes: 0GitHub stars: 37
- Quality AuditMeta-skill for auditing and validating skill quality. Use when reviewing skills for consistency, completeness, accuracy, and adherence to standards. Provides structured rubrics, scoring frameworks, and actionable recommendations.Votes: 0GitHub stars: 37
- Solid PhpUse when applying SOLID principles to Laravel 13 / PHP 8.3+ code — file size limits, interface placement, or PHPDoc enforcement.Votes: 0GitHub stars: 29
- Dev WorkflowsUse when running builds, executing tests, or improving developer experience workflows - provides structured guidance for build/test execution and DX improvement.Votes: 0GitHub stars: 37
- Pr SummarySummarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.Votes: 0GitHub stars: 29
- Code QualityCode quality validation with linters, SOLID principles, error detection, and architecture compliance across all languages.Votes: 0GitHub stars: 29
- Managing Tech DebtHelp users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring work, deciding between rewrites vs. incremental fixes, trying to get buy-in for tech debt reduction, or balancing new features with maintenance.Votes: 0GitHub stars: 1,301
- Systematic DebuggingSystematic methodology for debugging bugs, test failures, and unexpected behavior. Use when encountering any technical issue before proposing fixes. Covers root cause investigation, pattern analysis, hypothesis testing, and fix implementation. Use ESPECIALLY when under time pressure, "just one quick fix" seems obvious, or you've already tried multiple fixes. NOT for exploratory code reading.Votes: 0GitHub stars: 27
- Style Guide AdherenceUse when writing code - follow Google style guides where available, otherwise follow established best practices for the languageVotes: 0GitHub stars: 11
- Review ScopeUse before code review - determine if change is minor (review new code only) or major (review impacted code too)Votes: 0GitHub stars: 11
- Review GateHARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not metVotes: 0GitHub stars: 11
- No Deferred WorkUse during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permissionVotes: 0GitHub stars: 11
- Inclusive LanguageUse when writing code, documentation, or comments - always use accessible and respectful terminologyVotes: 0GitHub stars: 11
- Code Review全面的代码审查技能，分析代码质量、识别问题、安全漏洞，并提供带严重性评级的改进建议。Votes: 0GitHub stars: 85
- Deferred FindingUse when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development processVotes: 0GitHub stars: 11
- Branch DisciplineUse before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct baseVotes: 0GitHub stars: 11
- Sentry Code ReviewAnalyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.Votes: 0GitHub stars: 11