All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 15,938
- 665
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 15,217–15,240 of 15,938 skills
- WardenUse AFTER writing code and BEFORE submitting a PR. Simulates a strict code reviewer by comparing changes against reference files and documented conventions. Catches "we don't do it that way" feedback before your human reviewer does.Votes: 0GitHub stars: 5
- Devteam ReviewRun a coordinated code review across multiple reviewers. Launches the Code Review Coordinator to orchestrate language-specific and domain-specific reviewers.Votes: 0GitHub stars: 18
- Devteam Design DriftDetect design inconsistencies and drift from the design system. Launches the Design Drift Detector to analyze the codebase for deviations.Votes: 0GitHub stars: 18
- Devteam BugFix a bug with structured diagnostic workflow. Uses interview to clarify details and Bug Council for complex issues.Votes: 0GitHub stars: 18
- Evaluator Review ContractInternal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.Votes: 0GitHub stars: 14
- Evaluator Review Contract ParallelInternal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.Votes: 0GitHub stars: 14
- Verification Before Completion在宣称工作完成、已修复或测试通过之前使用，在提交或创建 PR 之前——必须运行验证命令并确认输出后才能声称成功；始终用证据支撑断言Votes: 0GitHub stars: 8,259
- Requesting Code Review完成任务、实现重要功能或合并前使用，用于验证工作成果是否符合要求Votes: 0GitHub stars: 8,259
- Pr AutofixWhen the user has PR review feedback to address, CI failures to fix, or wants to automatically resolve common PR issues. Use when the user says "fix the PR," "address review comments," "CI is failing," "fix the build," "autofix," "pr feedback," "resolve comments," "fix merge conflicts," or when a PR needs updates before merge. Reads the review comments, diagnoses issues, and applies fixes.Votes: 0GitHub stars: 4
- Code ReviewWhen the user wants a thorough code review of changes, a PR, a file, or a feature branch. Use when the user says "review this," "code review," "check my code," "what's wrong with this," "review my PR," "look over this," "critique this," "review before merge," or when submitting code for quality assessment. Performs multi-pass review covering correctness, security, performance, maintainability, and edge cases.Votes: 0GitHub stars: 4
- TuringStep-by-step logic tracer. Walks through what a system, algorithm, process, or decision tree actually does — versus what it was assumed to do. Finds the exact step where logic diverges from expectation. Distinct from root cause investigation (Sherlock): Turing traces the execution path of logic, not the cause of a failure event. Triggers on: "Turing", "trace this logic", "walk me through what this actually does", "where does this break down", "verify my logic", "step through this", "what does...Votes: 0GitHub stars: 4
- React DoctorDiagnose and fix React codebase health issues. Use when reviewing React code, fixing performance problems, auditing security, or improving code quality.Votes: 0GitHub stars: 365
- Fix Sentry IssuesUse Sentry MCP to discover, triage, and fix production issues with root-cause analysis. Use when asked to fix Sentry issues, triage production errors, investigate error spikes, or clean up Sentry noise. Requires Sentry MCP server. Triggers on "fix sentry", "triage errors", "production bugs", "sentry issues".Votes: 0GitHub stars: 365
- Verify And ShipChoose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.Votes: 0GitHub stars: 846
- DebugFull debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.Votes: 0GitHub stars: 846
- Zh Code Reviewer中文代码审查专家 - 生成详细的中文代码审查报告Votes: 0GitHub stars: 876
- Refactor Advisor重构顾问 - 识别代码坏味道并提供重构方案Votes: 0GitHub stars: 876
- Perf Profiler性能分析 - 识别瓶颈、生成优化建议Votes: 0GitHub stars: 876
- Eslint FixESLint 自动修复专家 — 识别 ESLint 报错，批量修复，支持常见规则和自定义配置Votes: 0GitHub stars: 876
- Diagnose Why Work StoppedHow to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code changes — gated by board/CTO approval before child issues are created. Use whenever the issue title or body asks for forensics on a stalled, looping, or "went too deep" tree.Votes: 0GitHub stars: 3
- Gh Address CommentsThis skill should be used when addressing GitHub pull request review comments systematically with mandatory resolution tracking. Use when user says "address PR comments", "fix review feedback", "handle PR review", "resolve PR threads", or needs to ensure all review comments are addressed before merging. Fetches comments via gh CLI, creates task checklists, links commits to review threads, and blocks completion if unresolved threads remain.Votes: 0GitHub stars: 73
- OptimizeBenchmark, analyze, and optimize a function's execution time. Produces a before/after performance table with real numbers. Never presents a change without proving it is faster.Votes: 0GitHub stars: 2
- Code ReviewReviews code diffs and files for security vulnerabilities (OWASP Top 10), error handling, complexity, naming conventions, and performance issues. Use when the user asks to review a PR, pull request, diff, merge request, or code changes.Votes: 0GitHub stars: 2,921
- Git Version ControlGit commit standards, branch strategy, and LLM-assisted development workflows. Use when making commits, managing branches, or working in high-velocity LLM-assisted development contexts. Covers atomic commits, conventional commits, branching strategies (trunk-based, GitHub flow), merge vs rebase decisions, and recovery patterns.Votes: 0GitHub stars: 9