Code Review

Automated code review and analysis

Showing 193-216 of 8780 skills
remix-run

write-api-docs

by remix-run

Write or audit public API docs for Remix packages. Use when adding or tightening JSDoc on exported functions, classes, interfaces, type aliases, or option objects.

Code Review 33.3K 3mo ago
remix-run

typescript-expert

by remix-run

Write, refactor, or review TypeScript code with strict, precise, maintainable types and without unnecessary any, type assertions, or type suppressions. Use when working on .ts or .tsx files, public APIs, generics, discriminated unions, type guards, tsconfig/module settings, declaration-facing code, or any change where TypeScript type quality affects correctness in the Remix repo.

Code Review 33.3K 3mo ago
remix-run

review-pr

by remix-run

Review Remix pull requests from a local development checkout. Use when asked to review a PR, inspect a pull request diff, or produce a thorough reviewer-style assessment.

Code Review 33.3K 3mo ago
elastic

codeql

by elastic

Work with CodeQL in Kibana — write, test, and debug custom queries locally, fetch scan results from GitHub, and validate inline suppression comments. Use when writing or debugging CodeQL queries, running CodeQL unit tests, analyzing SARIF results, fetching scan results, or checking codeql suppression justifications.

CLI Tools 21.3K 6mo ago
elastic

fix-package-docs

by elastic

Fix API documentation issues in a Kibana plugin or package. Use when asked to fix, improve, or add JSDoc/API documentation for a Kibana plugin or package, or when check_package_docs validation fails.

Code Review 21.3K 5mo ago
elastic

optimize-bundle-size

by elastic

Reduce plugin page load bundle size and avoid unnecessary increases in packages/kbn-optimizer/limits.yml. Use when proactively optimizing bundles, investigating CI page-load overages, or reviewing PRs that change bundle limits.

Code Review 21.3K 6mo ago
elastic

build-connector

by elastic

End-to-end orchestrator that creates a new connector from scratch, reviews the code, activates it in Kibana, tests it via an Agent Builder agent, iterates until quality is met, and delivers a polished result. Use when asked to build, develop, or implement a complete connector.

Code Review 21.3K 1mo ago
elastic

cypress-to-scout-migration

by elastic

Migrate Kibana Cypress E2E tests (.cy.ts) to Scout (Playwright). Applies to any Kibana plugin or solution. Includes triage gates (duplicate detection, layer analysis, value assessment), Cypress-to-Scout pattern mapping, data cleanup audit, and PR workflow. Use when: (1) migrating a Cypress test to Scout, (2) converting .cy.ts to .spec.ts, (3) planning a Cypress-to-Scout migration batch, (4) rewriting Cypress screens/tasks as Scout page objects, (5) asked "how do I move this Cypress test to Scout/Playwright", (6) asked about differences between Cypress and Scout.

Code Review 21.3K 19d ago
elastic

saved-objects-style-review

by elastic

Kibana Saved Objects registration and style review guidance. Use when creating, changing, or reviewing Saved Object changes involving savedObjects.registerType, mappings, modelVersions, root mappings, or Saved Objects type definitions.

Code Gen 21.3K 1mo ago
pollinations

manage-vast-gpu-fleet

by pollinations

"Inspect, price, canary, replace, and document Pollinations-operated Vast.ai GPU workers. Use for scheduled Vast offer scouting, GPU fleet cost or utilization reviews, preparing an isolated replacement, human-approved production cutovers, retiring replaced instances, and the follow-up repository PR."

Automation 5K 28d ago
dotnet

changewaves

by dotnet

'Manage MSBuild Change Waves: create new waves, condition features behind opt-out flags, write tests for wave-gated features, document change waves in ChangeWaves.md, and retire expired waves. Use when adding changes that need an opt-out or rotating out old change waves. Changes that introduce a user-visible behavior change should consider whether to use a changewave.'

Code Gen 5.5K 4mo ago
weapp-vite

weapp-vite-best-practices

by weapp-vite

面向采用 weapp-vite 项目布局仓库或已安装 weapp-vite 依赖项目的工程化实践手册,覆盖 vite.config.ts 的 weapp 配置、自动路由、routeRules/layout、buildScope、自动导入组件、分包、npm、六平台单目标构建、受管 TypeScript、HMR、sourcemap、prepare、MCP、Web runtime、lib mode、worker、AI skills,以及与 weapp-ide-cli 的命令治理边界。

Code Review 466 23d ago
x-cmd

x-ps

by x-cmd

Enhanced ps process viewer with interactive UI, fzf support, AI filtering, and CSV/JSON/TSV output formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

Code Gen 4.6K 5mo ago
x-cmd

x-smart

by x-cmd

SMART disk health monitoring tool. Check disk health, temperature, and attributes using smartctl. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

Code Review 4.6K 5mo ago
coder

tbench

by coder

Terminal-Bench integration for Mux agent benchmarking and failure analysis

CLI Tools 2K 1mo ago
reactjs

review-docs

by reactjs

Use when reviewing React documentation for structure, components, and style compliance

Code Review 11.8K 7mo ago
reactjs

react-expert

by reactjs

Use when researching React APIs or concepts for documentation. Use when you need authoritative usage examples, caveats, warnings, or errors for a React feature.

Automation 11.8K 7mo ago
vercel

update-docs

by vercel

This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.

Code Review 142K 7mo ago
dotnet

pr-finalize

by dotnet

Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation changed during review. Do NOT use for extracting lessons (use learn-from-pr), writing tests (use write-tests-agent), or investigating build failures (use azdo-build-investigator and ci-analysis).

Code Review 23.3K 3mo ago
dotnet

find-reviewable-pr

by dotnet

Finds open PRs in the dotnet/maui and dotnet/docs-maui repositories that are good candidates for review, prioritizing by milestone, priority labels, partner/community status.

Agents 23.3K 6mo ago
dotnet

try-fix

by dotnet

Attempts ONE alternative fix for a bug, tests it empirically, and reports results. ALWAYS explores a DIFFERENT approach from existing PR fixes. Use when CI or an agent needs to try independent fix alternatives. Invoke with problem description, test command, target files, and optional hints.

CLI Tools 23.3K 23d ago
dotnet

reviewing-compiler-prs

by dotnet

"Performs multi-agent, multi-model code review of F# compiler PRs across 19 dimensions including type checking, IL emission, binary compatibility, and IDE performance. Dispatches parallel assessment agents per dimension, consolidates with cross-model agreement scoring, and filters false positives. Invoke when reviewing compiler changes, requesting expert feedback, or performing pre-merge quality checks."

Code Review 4.3K 3mo ago
dotnet

binlog-analysis

by dotnet

Triage a build / compile / restore / WarnAsError failure from its MSBuild binary log. Fetches the binlog (a local build's, or a failed dotnet/fsharp Azure DevOps PR build's published artifact) and analyzes it live via the binlog-mcp MCP server — structured errors, root-cause diagnosis, and an MSBuild perf X-ray. NOT for test failures or CheckCodeFormatting: a build binlog has no errors there.

Code Review 4.3K 2mo ago
dotnet

postmortem

by dotnet

Write a postmortem for a regression that escaped to production, broke real users, and traces back to a design flaw worth documenting for future implementors. Only invoke after confirming no existing postmortem or doc covers the same root cause.

Code Review 4.3K 6mo ago