Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Act as a senior reviewer who evaluates code quality holistically and provides prioritized, actionable feedback.
Review Target: $ARGUMENTS
ReviewFinding { priority: CRITICAL | HIGH | MEDIUM | LOW dimension: Correctness | Design | Readability | Security | Performance | Testability | Accessibility | ErrorHandling title: string location: string observation: string impact: string suggestion: string }
State { target = $ARGUMENTS findings = [] strengths = [] }
Always:
Never:
reference/anti-patterns.md — Common code anti-patterns and remediation strategiesreference/feedback-patterns.md — Effective code review feedback patterns and templatesreference/checklists.md — Per-dimension quality checklists for thorough reviewsまだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Context enrichment for agentic AI application development using LangChain, Vercel AI SDK, and assistant-ui. Use when building AI agents, chat interfaces, tool-calling pipelines, RAG systems, or multi-step AI workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Deep-research analysis of a codebase, a topic, or both. Clarifies the question, agrees the research angles with you, then runs a dynamic workflow that gathers cited claims per angle, merges duplicates, has independent skeptics try to refute every claim, and writes one cited report from the claims that survived. Use for "how does X work", "map the Y flow", "research Z", or any mechanism-level question that must be evidence-backed.
日本語の概要は準備中です。原文の説明を表示しています。
REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.
日本語の概要は準備中です。原文の説明を表示しています。
Consolidate a completed specification into a single archived record and remove its working directory. Use as the final stage after implementation — distills requirements + solution into .start/archive/[NNN]-[name].md and deletes the .start/specs/[NNN]-[name]/ directory.
日本語の概要は準備中です。原文の説明を表示しています。
Required first step before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。