All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,948
- 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,185–14,208 of 14,948 skills
- Code HygieneReview your codebase for drift introduced by isolated AI sessions: dead exports, duplicate logic, and orphaned types.Votes: 0GitHub stars: 2
- Neo Code ReviewSystematically reviews source code for quality, performance, security, and style issues. Use this skill when the user submits code for review, asks for feedback or a code audit, wants to identify bugs/vulnerabilities, or requests a review of recent changes (such as git diff, staged changes, or a specific commit).Votes: 0GitHub stars: 7
- Learning QualityStructured format for capturing high-quality learnings during ClosedLoop runsVotes: 0GitHub stars: 121
- TribunalUse when completing tasks, implementing major features, or before merging to verify work meets requirementsVotes: 0GitHub stars: 68
- HunterUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 68
- ForgeUse when implementing any feature or bugfix, before writing implementation codeVotes: 0GitHub stars: 68
- FixVerify and fix BLOCKING/HIGH code review findings from a prior review session, then run project verification.Votes: 0GitHub stars: 122
- ArbiterUse when receiving code review feedback, before implementing any suggestion — requires technical verification and reasoned evaluation, not performative agreement or blind implementationVotes: 0GitHub stars: 68
- RefactoringRefactors code safely with test verification. Use when asked to refactor, restructure, clean up, or improve code organization.Votes: 0GitHub stars: 7
- Receiving FeedbackUse when receiving code review feedback or corrections - before implementing suggestions. Requires technical verification and reasoned evaluation, not blind agreement or performative responses.Votes: 0GitHub stars: 7
- DebuggingUse when encountering any bug, test failure, error, or unexpected behavior - before proposing fixes. Requires root cause investigation first.Votes: 0GitHub stars: 7
- Creating PrCreates pull requests with quality descriptions. Use when asked to create a PR, open a pull request, or ship code for review. Requires test verification before PR creation.Votes: 0GitHub stars: 7
- CommittingCreates quality git commits with conventional commit format. Use when asked to commit changes or create a commit message.Votes: 0GitHub stars: 7
- Pr Threads ResolveBulk resolve unresolved PR review threads. Useful after manually addressing threads or after using /pr-threads-address.Votes: 0GitHub stars: 517
- Pr Threads AddressReview all unresolved PR review threads, address them by making necessary code changes, and commit the changes appropriately.Votes: 0GitHub stars: 517
- Validate SpecsCross-validates BRD and PRD for coverage gaps, contradictions, and technical feasibility. This skill should be used when the user asks to "validate specs", "cross-validate BRD and PRD", "run Stage 2B", "validate specifications", "check spec consistency", "run spec validation", "verify BRD PRD alignment", or when the transmute-pipeline agent reaches Stage 2B of the pipeline.Votes: 0GitHub stars: 4
- RefactorAudits the codebase for code quality issues and refactors without changing external behavior. This skill should be used when the user asks to "refactor the codebase", "clean up code quality", "eliminate duplication", "improve abstractions", "enforce consistency", "remove dead code", or "optimize architecture" — or when the transmute-pipeline agent reaches Stage 6E of the pipeline.Votes: 0GitHub stars: 4
- OptimizeAudits and optimizes frontend, backend, and perceived performance against PRD budgets. This skill should be used when the user asks to "optimize performance", "run a performance audit", "improve page speed", "check Lighthouse scores", "fix Core Web Vitals", "reduce bundle size", "optimize queries", or "improve loading time", or when the transmute-pipeline agent reaches Stage 6C of the pipeline.Votes: 0GitHub stars: 4
- HardenHardens error handling, network failure recovery, and edge case resilience across the product. This skill should be used when the user asks to "harden error handling", "add resilience", "handle network failures", "add retry logic", "add circuit breakers", "handle edge cases", or "improve error recovery" — or when the transmute-pipeline agent reaches Stage 6G of the pipeline.Votes: 0GitHub stars: 4
- Review PrPre-PR review catching GitHub Copilot patternsVotes: 0GitHub stars: 16
- HardeningAudit and harden any repository with standardized quality gates, hooks, and scriptsVotes: 0GitHub stars: 16
- Process Pr ReviewsUse when the user asks to process, triage, fetch, view, count, list, or resolve review feedback in a GitHub PR. Supports both CodeRabbit and Codex review workflows. In this workflow, “real review feedback” is strictly defined as actionable inline comments; for CodeRabbit, exclude review summaries and nitpicks, and for Codex, exclude review summary cards and use PR main-thread reactions only as status signals.Votes: 0GitHub stars: 3,264
- Conductor DefectFix bugs reported by humans from a BUG.md file. Takes an application name (mandatory), version (optional — supports single version, comma-separated list, "all", or omit for all), and module (optional), resolves the context folder automatically from root-level application folders. When multiple versions are provided (or "all"/omitted), versions are processed SEQUENTIALLY in ascending semver order — all bugs from version N are fully resolved before version N+1 begins. Tags untagged bugs, cr...Votes: 0GitHub stars: 3
- OptimizingUse when optimizing a bundle-plugin or single skill — improving descriptions, reducing tokens, fixing audit findings, restructuring workflows, adding skills to fill gaps, or iterating on user feedbackVotes: 0GitHub stars: 230