250 free skills · page 5 of 5
Code Review skills
Skills for reviewing code well — structured checklists, spotting anti-patterns, and giving actionable feedback on pull requests.
Real files from public repositories — hand-curated, never invented. Sorted by installs.
5 / 5page
github-clioldwinter/skillsThis skill should be used when users need to interact with GitHub via the gh CLI. It covers repository management (create, delete, clone, fork), CI/CD workflows (GitHub Actions), Issues, Pull Requests, Releases, and other GitHub operations. Triggers on requests mentioning GitHub, repos, PRs, issues, actions, or workflows.Code Review147
task-pipelinessheleg/task-pipelineRuns a substantial task through a full delivery pipeline: an intake grill that locks the request into a brief, then docs study, brainstorm, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs/wiki sync and acceptance. Use when work changes the repository — a feature, fix, refactor, migration, integration, rewrite, adoption or hardening; фича, фикс, рефактор, миграция, интеграция, доработать, починить, внедрить, перевести — or when the output is a finding that lands in it: audit/аудит, bug hunt/проверь ошибки, production check/проверь прод, PR review/ревью PR — or on 'run this through the pipeline' / 'прогони по конвейеру', 'the full cycle' / 'полный цикл', /task-pipeline. Two modes need no task at all: 'checkup' / 'чекап' reports what shipped unconfirmed and what to look at first; 'setup' audits existing documentation. Not for: answering a question, explaining code, a typo or a one-line edit — say 'без пайплайна' / 'quick' to opt out.Code Review141
clean-code-ts-reactpproenca/dot-skillsUse when writing, reviewing, or refactoring TypeScript or React code for craftsmanship — naming, function and component shape, error handling, data modeling, tests, and abstraction. Translates Robert C. Martin's Clean Code principles into modern TS+React idioms (TS 5.x, React 19), with first-class "When NOT to apply" guidance and a Meta category for principle conflicts (DRY vs SRP, small functions vs deep modules, type safety vs ergonomics). Triggers on code review, refactoring for clarity, naming, function/component design, "is this clean?", "make this more readable", "right abstraction?" — even when the user doesn't say "clean code". Does NOT cover React-specific APIs (RSC, hooks API surface) — use the react skill. Does NOT cover TS compiler perf or tsconfig — use the typescript skill.Code Review140
adversarial-reviewbasicmachines-co/basic-memoryCross-vendor adversarial code review of the current branch. Two different model families (Claude + Codex/GPT) review the diff independently, then try to refute each other's findings; survivors are reported by confidence. Runs from either Claude Code or Codex. Use when the user asks for an adversarial review, a cross-model / second-opinion review, or wants high-confidence findings before merging. Report-only — never auto-applies fixes.Code Review139
diffx-finish-reviewwong2/diffxFinish a code review session by fetching comments from the running diffx server, applying requested changes, and marking comments as resolved. Use when the user invokes /diffx-finish-review.Code Review138
code-review-standardsbobmatnyc/claude-mpm-skillsSeverity-tagged code review checklist (CRITICAL/HIGH/MEDIUM/LOW) used by code-critic agentCode Review135diffx-start-reviewwong2/diffxStart a code review session by launching the diffx server and opening the browser UI. Use when the user invokes /diffx-start-review.Code Review135
code-reviewsiviter-xyz/dot-agentCode review practices emphasizing technical rigor, evidence-based claims, and verification. Use when receiving code review feedback, completing tasks requiring review, or before making completion claims.Code Review133
code-reviewerrightnow-ai/openfangCode review specialist focused on patterns, bugs, security, and performanceCode Review131
llm-judgeexistential-birds/beagleUse when comparing two or more code implementations against a spec or requirements doc. Triggers on \"which repo is better\", \"compare these implementations\", \"evaluate both solutions\", \"rank these codebases\", or \"judge which approach wins\". Also covers choosing between competing PRs or vendor submissions solving the same problem. Does NOT review a single codebase for quality \u2014 use code review skills instead. Does NOT evaluate strategy docs \u2014 use strategy-review. Requires a spec file and 2+ repo paths.Code Review125Other tasks
same rules, different job
