Code Review
863 skills.
Browse
reference-coreangularExplains the mental model and architecture of the code under `packages/core`. You MUST use this skill any time you plan to work with code in `packages/core`cookbook-auditanthropicsAudit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.skills-qaanthropicsEvaluate a skill against the Legal Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three legal failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as partramsartivillaRun accessibility and visual design review on components. Use when reviewing UI code for WCAG compliance and design issues.code-slopasyrafhussinDetect AI-generated code patterns ("slop") in PHP/Laravel and TypeScript/React source — comment narration, generic naming, premature interfaces, defensive overdose, mock-everything tests, and the absence of human "scars". Use when reviewing AI-assisted PRs, auditing code for taste/quality (not metrics — that's technical-debt), or hardening a code-review checklist. Triggers on "review for AI slop", "find AI patterns", "check code feels human", "audit code-quality taste".technical-debtasyrafhussinTechnical debt inventory, prioritization, and audit for PHP/Laravel (MySQL) and Node/TypeScript/React projects. Use when assessing code health, identifying refactoring candidates, planning debt paydown, or auditing a codebase for accumulated debt. Triggers on "audit technical debt", "find tech debt", "debt inventory", "what should we refactor first", or tasks involving code health, security debt, performance debt, data debt, observability debt, debt prioritization, or remediation planning.web-design-guidelinesasyrafhussinUI/UX best practices and accessibility audit. Use when reviewing UI code, checking accessibility, running accessibility audits, auditing forms, or ensuring web interface best practices. Triggers on "audit accessibility", "check WCAG", "review UI", "check accessibility", "audit design", "review UX", or "check best practices".code-review-skillawesome-skillsProvides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C#/.NET, Kotlin, Swift, Dart, Flutter, NestJS, C/C++, Zig, CSS/Less/Sass, Qt, and more. Covers architecture review, performance review, security audit, code quality anti-patterns, and common bugs across all ecosystems. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing reviewarchitectbacknotpropSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.blast-radiusbacknotpropFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.howbacknotpropUse for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.interrogatebacknotpropUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.no-commentsbacknotpropSpawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.principle-attack-the-premisebacknotpropApply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.principle-boundary-disciplinebacknotpropApply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.principle-fix-root-causesbacknotpropApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.principle-foundational-thinkingbacknotpropApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.principle-laziness-protocolbacknotpropApply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.principle-make-operations-idempotentbacknotpropApply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.principle-migrate-callers-then-delete-legacy-apisbacknotpropApply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.principle-minimize-reader-loadbacknotpropApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.principle-model-the-domainbacknotpropApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.principle-outcome-oriented-executionbacknotpropApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.principle-redesign-from-first-principlesbacknotpropApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.principle-separate-before-serializing-shared-statebacknotpropApply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.principle-sequence-verifiable-unitsbacknotpropApply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.principle-subtract-before-you-addbacknotpropApply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.principle-type-system-disciplinebacknotpropApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.wordpress-performance-best-practicesbartekmisWordPress performance optimization guidelines for plugin, theme, and custom code development. This skill should be used when writing, reviewing, or refactoring WordPress PHP code to ensure optimal performance patterns. Triggers on tasks involving WP_Query, database queries, caching, hooks, REST API, or WordPress theme/plugin development.codex-reviewbenedictkingProfessional code review skill for Claude Code. Automatically collects file changes and task status, and proactively fixes P0/P1/P2 issues after review. Triggers when working directory has uncommitted changes, or reviews latest commit when clean. Triggers: code review, review, 代码审核, 代码审查, 检查代码ss-a11ybitjaruAudit a component or page for accessibility issues and fix themss-reviewbitjaruReview UI code for design system compliance, accessibility, and best practicesreview-fix-address-botsbiwIntegrate the PR base, run persistent read-only reviewers, fix and re-review findings, validate with repo-native commands, address review bots, and compare model quality.w-a11yblockmaticAudit UI against repository a11y docs and tests; do not invent a WCAG level.w-architectureblockmaticPlan an implementation structure; durable decisions belong in ADRs and architecture docs.w-coderabbitblockmaticFetch CodeRabbit review comments, apply authorized fixes, and stop at local verification.w-commentsblockmaticProcess reviewer feedback, apply required fixes, and draft replies without unsolicited commits.w-deslopblockmaticRemove AI-generated slop introduced on this branch relative to main.w-errorsblockmaticAdd error handling that matches existing repo error and logging packages.w-lintblockmaticRun project linters, apply the smallest fixes, and re-run until the suite is clean.w-perfblockmaticMeasure bottlenecks with repository tools, then recommend or apply evidenced optimizations.w-refactorblockmaticRefactor selected code while preserving behavior, then verify.w-releaseblockmaticAdvisory review of release impact, changelog, and template contracts.w-reviewblockmaticReview a change for evidenced defects and risks without editing it.typescript-clean-codebmad-labsClean Code for TypeScript — code smell catalogs (Martin's per-line heuristics, Fowler's change-shape smells, TypeScript-native type smells), a linter-first detection policy, and step-by-step review, refactoring, TDD, and estimation workflows. Use when the user: - Writes, reviews, or refactors TypeScript/JavaScript code, or asks whether code is clean, maintainable, or well-designed - Names a smell — Shotgun Surgery, Feature Envy, Data Clumps, Long Method, Divergent Change, Duplicated Code, Large mypybobmatnycmypy - Static type checker for Python with gradual typing, strict mode, Protocol support, and framework integrationvisual-recapbuilderioTurn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.web-design-guidelinescalesthioReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".capacitor-accessibilitycap-goAccessibility guide for Capacitor apps covering screen readers, semantic HTML, focus management, and WCAG compliance. Use this skill when users need to make their app accessible.axiom-accessibilitycharleswiltgenUse when fixing or auditing ANY accessibility issue — VoiceOver, Dynamic Type, color contrast, touch targets, WCAG compliance, App Store accessibility review.