🔍代码审查 / GitHub MCP 推荐

Improve the shape of existing code without changing behavior.

TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.

Running and debugging tests in the Golem workspace. Use when writing tests, running specific tests, filtering tests, debugging test failures, or understanding test infrastructure.

Inspect pod logs, analyze resource quotas, trace network policies, check deployment rollout status, and run cluster health checks for Kubernetes. Use this skill when diagnosing Kubernetes cluster issues, debugging failing pods, investigating network connectivity problems, analyzing resource usage, troubleshooting deployments, or performing cluster health checks.

Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.

Use when semantic refactoring is needed in Rider-supported solutions and projects, including .NET/C#, F#, VB, C++, Unity, Unreal Engine, XAML, Razor, and other GameDev or mixed-language projects. Trigger when edits must update declarations and usages across IDE-resolved references — rename symbols, move types or namespaces, safe-delete unused code, extract interface/base class/method, change signatures, or reorganize namespaces. Do not use for file-only moves, config keys, strings, comments, prose-only edits, generated output, or logic changes with unchanged names/signatures.

React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code involving components, Next.js pages, Server Components, Server Actions, data fetching, bundle size, rendering behavior, or performance improvements.

Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.

Marin house writing style. Use when drafting or revising Marin-authored prose.

Use this skill before writing any SQL query. Covers: output shape inference (cardinality clues from the question), efficient schema exploration, iterative CTE-based query building, structured verification loop (row count, NULL audit, fan-out check, sample inspection), error recovery protocol, saving output to result.sql and result.csv, turn budget management, and common benchmark traps.

Equips cursor-ide-worker-bee to own Hivemind's Cursor surface: the Cursor 1.7+ hooks harness (~/.cursor/hooks.json, 6 lifecycle events) wired by src/cli/install-cursor.ts, the first-party VS Code/Cursor extension at harnesses/cursor/extension/, registering the Hivemind MCP server (src/mcp/server.ts) in Cursor, and the .cursor/ Bee Army platform this repo ships (rules .mdc format, agents, skills/Stingers, the-beekeeper/the-smoker commands, model-comparison-matrix). Use when the task touches Cursor hook wiring, .cursor/rules/*.mdc authoring, MCP registration in Cursor, the cursor extension build, or the Army's .cursor/ structure. Do NOT use for code quality of TS source (typescript-node-worker-bee), the MCP protocol internals of server.ts (mcp-protocol-worker-bee), or harness wiring for Claude/Codex/other agents (harness-integration-worker-bee).

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Design a ThinkWork Automation from a prompt by interviewing for goal, Space, trigger, verification, judge settings, stop guards, and privacy boundaries, then emit a reviewable AutomationDraft.

Execute research code inside isolated Docker containers for safe replication, experiments, and benchmarks. Use when the user selects Docker as the execution environment or asks to run code safely, in isolation, or in a sandbox.

리팩토링 분석 전문가. 기존 코드베이스를 컨벤션 기준으로 분석. Zero-Tolerance 위반 탐지, 영향도 분석, 단계별 리팩토링 계획 수립. /refactor-plan 명령 시 자동 활성화. Serena Memory에 결과 저장.

Design and implement RESTful API endpoints with proper HTTP methods, status codes, and consistent naming conventions. Use this skill when creating or modifying API routes, endpoints, or server-side request handlers. When working on files in src/pages/api/, files containing API route definitions, files implementing REST endpoints, files handling HTTP requests and responses, server middleware for API requests, API authentication and authorization logic, and files defining API versioning strategies. When designing URL structures for resources, implementing query parameter handling for filtering/sorting/pagination, setting up rate limiting for API endpoints, or configuring CORS and API security headers.

Design and implement RESTful API endpoints following best practices for URL structure, HTTP methods, status codes, versioning, and rate limiting. Use this skill when creating or modifying API routes, controllers, endpoint handlers, or route files. When working on files like routes.ts, api/*.ts, controllers/*.ts, endpoints/*.py, views.py, or any server-side request handlers. When designing resource URLs, implementing CRUD operations, adding query parameters for filtering/sorting/pagination, or setting up API versioning. When reviewing or refactoring existing API code for REST compliance.

Design and implement RESTful API endpoints following REST principles with resource-based URLs, appropriate HTTP methods, and consistent naming conventions. Use this skill when creating or modifying API route handlers, endpoint definitions, or REST controllers in files like routes.py, api.ts, controllers/, handlers/, or when implementing HTTP methods (GET, POST, PUT, PATCH, DELETE). Also applies when working on API versioning, request/response validation, status code handling, rate limiting, or any backend endpoint logic that serves HTTP requests to frontend clients or external systems.

Design and implement RESTful API endpoints following REST principles, HTTP standards, and resource-based URL conventions. Use this skill when creating or modifying API endpoints, routes, controllers, request handlers, or API documentation. Apply when working with REST API design, API versioning, HTTP methods (GET, POST, PUT, PATCH, DELETE), URL structure, query parameters, response formatting, status codes, rate limiting, or API middleware. Use when building web services, microservices, or any backend code that exposes HTTP endpoints for client consumption.

Design and implement RESTful API endpoints following best practices for routing, versioning, and HTTP standards. Use this skill when creating or modifying API routes, controllers, or endpoints in files like routes/api.php, API controller files in app/Http/Controllers/Api/, controller files in app/Http/Controllers/, API resource classes, or when implementing REST API functionality. Use when working on URL structures, HTTP method handling (GET, POST, PUT, PATCH, DELETE), API versioning strategies, query parameter handling for filtering/sorting/pagination, HTTP status code responses, rate limiting configuration, or any API endpoint design decisions.

Accesses the claude-mem MCP server from Cursor to search session history and record observations. Triggers: memory search, claude-mem, past decisions, record this. Do NOT load for: normal coding, temporary notes, or implementation work.

Accesses the claude-mem MCP server from Cursor to search session history and record observations. Triggers: memory search, claude-mem, past decisions, record this. Do NOT load for: normal coding, temporary notes, or implementation work.

Specialized agent for Cursor IDE integration and workflows.

Apply when defining API request/response types, DTOs, and shared types between frontend and backend.

Apply when building API endpoints in Next.js App Router using Route Handlers.

REST API development with Next.js 15 App Router. Dual authentication (API Key + Session), dynamic entities, metadata system. Use this skill to create endpoints, validate APIs, or understand API patterns.

Validate and repair the OSS first-install Docker Compose path. Use when editing docker-compose.yaml, docker-compose.dev.yaml, .env.example, release image tags, Compose profiles, Keycloak/OpenFGA/RAG defaults, or first-launch UI behavior for local all-in-one installs.

蒸馏并应用当前仓库的 Next.js Nextra 启动模板架构、已实现功能、二次开发扩展点与迁移模式。适用于理解本项目、继续二次开发、修改 docs/landing/i18n/theme/auth/UI 行为，或把这些 Next.js 16 + Nextra 4 + Tailwind CSS 4 模式复用到其他项目。

Distill and apply this repository's Next.js Nextra starter architecture, implemented features, extension points, and migration patterns. Use when Codex needs to understand this project, continue second-stage development, add or change docs/landing/i18n/theme/auth/UI behavior, or reuse these Next.js 16 + Nextra 4 + Tailwind CSS 4 patterns in another project.

用于火山引擎（Volcengine）数据库（MySQL、veDB-MySQL、PostgreSQL、SQL Server、MongoDB、Redis）和公网自建数据库（MySQL和PostgreSQL系列）的元数据管理、数据分析、开发变更、运维诊断、巡检。覆盖实例列表查询、实例下数据库列表查询、表列表查询、表结构查询、数据查询、数据分析与可视化报告（含跨数据源/文件联合分析）、数据治理（资产盘点/数据画像/数据质量/敏感数据识别）、慢查询诊断、死锁与锁等待分析、事务与活跃会话排查、错误日志查询、表空间分析、健康巡检、监控指标查询、变更工单申请等场景。不支持字节云（ByteCloud）数据库，如 ByteRDS / ByteDoc / ByteRedis。

MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git work.

Use when a React Native app uses or is choosing the react-native-video library — playing/controlling video or audio, the v6 `Video` component or the v7 `useVideoPlayer`/`VideoView` player API, source/props/events (onLoad, onProgress, onEnd, paused, resizeMode, source, drm), HLS/DASH, DRM (Widevine/FairPlay, `@react-native-video/drm`), captions/tracks, Picture-in-Picture, background or lockscreen audio, fullscreen, buffering, offline/downloading, or native iOS/Android setup; also when deciding between v6 and v7 or migrating between them. Triggers on "react-native-video", "RNV", `Video`, `useVideoPlayer`, `VideoView`, and similar.

Working on the RomM Python backend (backend/) — a FastAPI app with SQLAlchemy 2.0, Alembic, RQ/Redis, and Socket.IO. Use when adding or changing API endpoints, handlers, ORM models, response schemas, metadata-provider adapters, background tasks, database migrations, or backend tests. Covers the layered architecture, conventions, auth/scopes, the OpenAPI→frontend type pipeline, and the uv/pytest/alembic/trunk workflow. Trigger on any work under backend/.

Theming, design tokens, colors, and visual language in the RomM v2 frontend. Use when styling v2 components, picking colors, adding/using CSS variables, working with light/dark themes, or whenever you'd reach for a hex/rgba literal. Covers the token pipeline (src/v2/tokens/index.ts → build:tokens → tokens.css), the .r-v2 scope classes, the zero-hex-literal policy, and shared state semantics. Trigger on any color/theme/token work under frontend/src/v2/.

Cross-cutting feature patterns for the RomM v2 frontend — error/snackbar handling, loading & skeleton states, real-time Socket.IO updates, UI state persistence (URL vs localStorage vs ephemeral), pagination/infinite scroll, forms & validation, permissions (useCan), and destructive confirmations. Use when wiring up a v2 feature's behavior (not just its markup). Trigger when implementing data flows, dialogs, forms, toggles, or permission gating under frontend/src/v2/.

Building or modifying components in the RomM v2 frontend (frontend/src/v2/). Use when creating/editing v2 primitives (R* components in src/v2/lib/), shared composites, or feature composites — covers the three-tier model, file/folder conventions, SFC structure, import order, barrels, Storybook requirements, and v2 anti-patterns. Trigger on any work under frontend/src/v2/.

Universal input (mouse, touch, keyboard, gamepad) and responsive/universal-viewport layout in the RomM v2 frontend. Use when adding interactive v2 components, focus management, spatial navigation, gamepad/keyboard handling, modality-gated focus rings, breakpoints, or responsive layout. Covers useInput, focus geometry primitives, the overlay scope stack, useBreakpoint, and the data-bp/data-input attributes. Trigger on interactive or responsive work under frontend/src/v2/.

Use when creating, updating, or improving agent skills.

Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.

Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.

Design new small-molecule binders with Boltz. Use when generating novel ligands or hits for a target without a fixed compound library. Not for screening existing molecules or one-off docking.

Design new protein binders with Boltz. Use when generating protein, peptide, antibody, nanobody, or custom binder candidates for a target. Not for screening existing proteins or small molecules.

How to update the bundled SQLite3 amalgamation (sqlite3/sqlite3.c and sqlite3.h) and the Meson wrap. Use when upgrading SQLite, refreshing the vendored amalgamation, or bumping the sqlite3 wrap.

SQLiteCpp release procedure: bump the version across all files, finalize the CHANGELOG, open the Release PR, and tag. Use when cutting a new release, bumping the project version, or tagging.

SQLiteCpp branch naming and creation rules for starting tasks, issues, or features.

Deploy a Worker live, no account, via wrangler --temporary.