'code-review' 검색 결과

Write Chinese code review feedback that clearly distinguishes required fixes, suggestions, and optional advice. Use question and suggestion templates, organize review summaries, and follow guidance for mixed Chinese-English comments and commit messages.

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

• Writing Chinese review comments with clear priorities
• Rephrasing blunt feedback as questions or suggestions
• Standardizing Chinese-English comments and commit messages

명세서나 티켓의 작업을 코드로 구현합니다. 유형 검사와 테스트로 확인하고 code-review 스킬로 변경 사항을 검토한 뒤 현재 브랜치에 커밋합니다.

• 명세서에 따른 기능 구현
• 지정한 티켓의 작업 구현
• 유형 검사와 테스트로 변경 사항 확인

Run a final pull request review using separate agents for each available review skill. Collect all reported issues into a numbered Markdown list, with a specific file path and line number for every finding.

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

• Run a final review of a pull request
• Combine findings from multiple review skills
• Locate issues by file path and line number

Build or refresh a knowledge graph, a map of code relationships used for code review. Choose a full rebuild or an incremental update, then report the operation's status and summary.

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

• Setting up the graph for a repository's first review
• Refreshing the graph after switching branches
• Updating review data after a large refactor

Always use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verification gates (run the command, read the output, then make the claim). Never skip — the cost of false completion claims is higher than the cost of verifying. References: code-review-reception.md, requesting-code-review.md, verification-before-completion.md.

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

code-review-scanner と code-review-critic による2フェーズレビュー。 大きなPRや複雑な変更を丁寧にレビューしたいときに使う。 scanner がトリアージして重要な指摘だけ critic が深掘りする。 軽いチェックには /review（4並列専門レビュー）を使う。

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

기능 구현 후나 병합 전에 별도 에이전트에 코드 리뷰를 요청합니다. 변경 내용과 요구 사항, 대상 커밋을 전달하고 지적된 문제의 심각도에 따라 수정을 진행합니다.

• 주요 기능 구현 후 리뷰
• 병합 전 변경 내용 확인
• 복잡한 오류 수정의 제삼자 검토

Review GitHub pull requests with specialized AI agents that check security, performance, architecture, and coding conventions. Generate actionable comments with suggested fixes, and connect review findings to automated approval or change requests.

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

• Reviewing authentication changes for security issues
• Checking database changes for performance regressions
• Reviewing UI accessibility and coding conventions

Take a pull request through repeated code review and fixes, verify that automated checks pass for the latest commit, and combine its changes into one commit when merging. Conflicts with the request’s goal require confirmation.

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

• Reviewing, fixing, and merging a pull request
• Resolving every review finding, including minor issues
• Checking CI results for the commit being merged

Review Git changes with the ocr command-line tool and a configured AI model. Get line-level findings grouped by severity for working changes, commits, or branch comparisons, with code fixes applied when explicitly requested.

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

• Reviewing changes before a commit
• Checking a pull request or branch comparison
• Inspecting a specific commit for issues

Let the host AI agent review Git changes while ocr selects files and resolves review rules. Receive findings grouped by severity, plus coverage details showing which files were reviewed or skipped and why.

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

• Reviewing changes with the current AI agent
• Checking branch differences or a single commit
• Reviewing files against their applicable rules

Review a defined code change through independent code and architecture reviewers. Receive severity-rated findings with file and line references, concrete fixes, and a final recommendation on whether the change is ready to merge.

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

• Checking a pull request before merging
• Assessing code quality and security within a defined scope
• Reviewing architectural boundaries and hidden dependencies

Comprehensive GitHub code review with AI-powered swarm coordination

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

PR 提出前にコードオーナー視点でフルレビューする。WHY の理解 → 設計 → AST/基盤型 → 実装（複数 Agent の順次レビュー）の順に、各フェーズでユーザーと対話しながら指摘を修正し、品質に問題がなくなるまで繰り返す。「/full-code-review」「フルレビュー」「レビューして」などの依頼時に使用。rsvelte（公式 Svelte コンパイラの Rust ポート）専用。

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

Dispatch code-reviewer agent for two-stage review. Use after completing implementation tasks.

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

Agent skill for code-review-swarm - invoke with $agent-code-review-swarm

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

Multi-agent code review using the Pragmatic Quality framework. Orchestrates parallel review agents (CLAUDE.md compliance, bug scanning, git history, security) with independent confidence scoring to produce high-signal findings. Use when user runs /code-review, /review:code-review, requests a "code review", "review my changes", "PR review", or mentions "review diff", "review branch".

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

Cursorでreviewer等から割り当てられた観点を評価する担当用native入口。共有code-review-guidanceと担当referenceを読み、結果を親へ返す。

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

Code-review quality gate and test-enhancement rubric. Use when ROSE needs sharper review output contracts, severity and risk prioritization, evidence anchors, negative review cases, fixture or golden-output drift guidance, or a Chinese review report profile; do not use as a duplicate code-review agent or final PASS authority.

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

Review GitHub pull requests, or proposed code changes, with specialized agents covering security, performance, architecture, and style. Generate actionable comments, apply quality thresholds, and coordinate automated review workflows.

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

• Review authentication changes for security issues
• Assess performance impacts of database changes
• Check UI accessibility and coding conventions

Review changed code from four angles: reuse, simplicity, efficiency, and whether fixes address the underlying mechanism. Applies suitable improvements within the reviewed scope while preserving intended behavior, and reports fixes or skipped findings.

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

• Clean up code changes before committing
• Replace duplicated logic with existing helpers
• Reduce redundant computation and repeated I/O

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

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

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Explore an unfamiliar codebase using a graph of code relationships. Inspect its structure, find functions and classes, trace calls and imports, follow execution paths, and locate large functions for closer investigation.

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

• Understanding the structure of an unfamiliar codebase
• Finding functions and classes by name or keyword
• Tracing calls, imports, and execution paths

Review code changes for security, performance, correctness, and maintainability. Get findings tied to files and lines, severity ratings, practical suggestions with code examples, and a recommendation to approve, request changes, or discuss further.

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

• Reviewing a pull request before merging
• Checking authentication and injection risks
• Finding excessive database queries and resource leaks