'correctness' 검색 결과

差分で新規に導入された import・メソッド呼び出し・ライブラリ API 参照が実在するかを code_search で検証し、AI 生成コード特有の幻覚的参照（存在しない関数・メソッド・モジュール・引数シグネチャ）を検出する

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a repository change for correctness, security, and maintainability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review FriendlyBet quality, regression risk, test plans, release readiness, version bump discipline, scoring/locking correctness, provider fallback behavior, and dirty-worktree safety. Use before shipping app code, scoring changes, migrations, sports integrations, copy updates, PWA cache changes, or any risky user-facing flow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate documentation before merging - check completeness, broken links, code example accuracy, and factual correctness. Use when reviewing docs for quality gates or running pre-merge doc validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review working changes - code quality, security, library correctness, and standards auto-fix

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fan six specialist reviewers (general correctness, silent failures, type design, test gaps, comment accuracy, simplification) out over the current diff, a branch, or a PR in parallel, then merge their findings into one deduplicated, ranked report. Use for a thorough review before merging. Not for editing code or approving on someone's behalf.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Improve clarity and reduce needless complexity after behavior is understood; preserve behavior and keep cleanup separate from correctness fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or editing the code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement and review iOS 26+ SwiftUI Liquid Glass UI. Use when adopting Liquid Glass or checking its correctness, performance, and design fit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deep, excruciating code review. Use anytime to analyze code for correctness, edge cases, security, performance, and design issues. Not tied to baseline—this is pure code analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Delegate writing predictable code to the `code-write` command, which has a cheaper writer model write the target file directly so the generated code never enters your context. Use for tests, scaffolding, fixtures, boilerplate, or a new file that copies an existing pattern, and when the user says "code write", "生成を委譲", or "雛形を書かせて". Do NOT use for design decisions, changes to public contracts or shared modules, edits inside an existing file that needs judgment, or logic with subtle correctness requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Delegate reading large or multiple files to the `bulk-read` command, which sends the files to a cheaper reader model and returns only its answer. Use when a question needs the content of a file over about 350 lines or of several files at once, when a PreToolUse guard denied an unbounded read, or when the user says "bulk read", "一括読み込み", or "まとめて読んで". Do NOT use for files you are about to edit, for subtle correctness reasoning such as concurrency bugs, or for short files that fit a bounded read.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Check your work with a verification subagent. Spawns a verifier that reviews diffs, runs builds and tests, and evaluates correctness. Use when asked to "check work", "verify changes", "self-verify", "/check", "/verify", "/check-work", or "/self-verify".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Perform a thorough code review focused on correctness, maintainability, performance, and best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run four parallel read-only subagents that each review the same diff from a different lens — security, performance, correctness, and readability — then merge findings into one report. Use before merging large or risky PRs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrates an end-to-end de novo genome assembly project, routing each step to the right genome-assembly skill rather than restating it. Profiles the genome first (k-mer spectrum -> size, heterozygosity, ploidy), QCs reads, chooses an assembly path by data type (SPAdes for Illumina, Flye for noisy long reads, hifiasm for HiFi, metaFlye for communities), polishes only when needed, decontaminates, scaffolds with Hi-C, and finishes with three-axis QC (contiguity + completeness + correctness). Use when assembling a genome from raw reads and deciding which assembler, whether to polish, and how to prove the result is good.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.