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,113–14,136 of 14,948 skills
- RefactoringSafe, behavior-preserving code transformation backed by tests. Refactor with evidence, not instinct.Votes: 0GitHub stars: 65
- Performance OptimizationMeasure first, optimize second. Data-driven performance improvements with before/after benchmarks and production validation.Votes: 0GitHub stars: 65
- Verification LoopA comprehensive verification system for Claude Code sessions.Votes: 0GitHub stars: 59
- Git WorkflowTrunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.Votes: 0GitHub stars: 65
- Error HandlingGraceful degradation and meaningful error messages. Errors are first-class citizens, not afterthoughts. Every error path is designed, not discovered.Votes: 0GitHub stars: 65
- Debugging MethodologySystematic root cause analysis for production and development bugs. Hypothesis-driven debugging — never guess-and-check.Votes: 0GitHub stars: 65
- Code ReviewStructured code review focusing on correctness, security, and maintainability. Correctness before style. Every reviewer comment must be actionable.Votes: 0GitHub stars: 65
- Code ExplanationGet layered, context-aware explanations of unfamiliar code. Understand what it does, why it was written that way, and how to work with it safely.Votes: 0GitHub stars: 65
- Systematic DebuggingDiagnose and fix bugs through four strict phases. Never guess — every hypothesis is tested with evidence before a fix is applied. ---Votes: 0GitHub stars: 8
- Progressive RefinementProduce a working solution first, then iteratively improve the weakest quality dimension. Each pass is measured before and after to prevent regressions. Stop when all dimensions meet threshold or the budget is exhausted. ---Votes: 0GitHub stars: 8
- Pre Landing ReviewAnalyze the current branch's diff against main for structural issues that tests don't catch. Two-pass review: Critical issues block merge; Informational issues are advisory. Read-only by default — only modifies files if user explicitly chooses to fix a critical issue. ---Votes: 0GitHub stars: 8
- Plan ReviewThoroughly review an engineering plan before any code is written. Combines an engineering review (architecture, code quality, tests, performance) with mode selection for scope posture. Interactive: one issue per question, opinionated recommendations, required completion summary. ---Votes: 0GitHub stars: 8
- Performance OptimizationImprove performance through measurement-driven cycles. Never optimize without a baseline. Never ship an optimization that breaks tests. ---Votes: 0GitHub stars: 8
- Code ReviewEvaluate code changes across four dimensions: security, quality, performance, and maintainability. Produce findings with severity ratings and concrete fix suggestions. ---Votes: 0GitHub stars: 8
- Careful RefactorImprove code structure without changing observable behavior. Use the Mikado method: one atomic step at a time, with test verification after every step. ---Votes: 0GitHub stars: 8
- Adversarial ReviewComplete the primary implementation, then switch roles: become an attacker whose goal is to break your own work. Write adversarial test cases, probe edge cases, attempt common exploit patterns, and challenge architectural decisions. Fix everything found. Repeat up to 3 attack-fix cycles. ---Votes: 0GitHub stars: 8
- Repo MaintainerChampionship-grade repository maintenance. Audits for test artifacts, dependency issues, CI/CD health, documentation sync, and FAF alignment. Generates prioritized cleanup plans. Use when repos need deep cleaning or ongoing maintenance.Votes: 0GitHub stars: 4
- Git Pr Review当用户明确要求审查 GitHub PR、评估是否合并或判断 PR 应如何处理时使用。对 PR 做只读、证据驱动的方案与风险评估,并给出合并建议。⚠️ 不适用:直接修改、合并 PR,或在本地执行不可信 PR 代码。Votes: 0GitHub stars: 48
- Systematic Debugging用于遇到缺陷、测试失败或异常行为,且必须在提出修复方案前调查根因的场景。未经根因分析不得只修复表象。Votes: 0GitHub stars: 48
- Code Reviewer用于审查已完成的工作、重大功能或合并前的变更,核对需求并按严重程度识别风险。未经审查不得合并。Votes: 0GitHub stars: 48
- Systematic DebuggingUse when encountering any bug, test failure, unexpected result, or failed replication - before proposing fixes or explanationsVotes: 0GitHub stars: 7
- Refine SpecReview a PRD or spec for completeness, ambiguity, edge cases, and acceptance criteria quality. Present structured findings by severity and offer to fix issues directly.Votes: 0GitHub stars: 31
- Qodo Pr ResolverReview and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)Votes: 0GitHub stars: 193
- Get Qodo RulesLoads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.Votes: 0GitHub stars: 193