Results for “code-review”

中文 review 沟通参考——话术模板、分级标注（必须修复/建议修改/仅供参考）、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用，不要根据上下文自动触发。

The English summary is being prepared. Showing the original description.

Code review by several models at once — Claude sub-agents, OpenAI Codex, and a cheap third reviewer via OpenCode — reconciled into one report. Reviews whatever is named: a diff, a branch, specific files, one function, a legacy module, a whole repo. Use for any review request, a second or third opinion, a cross-check before a PR, or "code-review", "multi", "consensus review".

The English summary is being prepared. Showing the original description.

Perform thorough code reviews with actionable, prioritized feedback. Use when a user asks to review code, check code quality, find bugs, review a pull request, audit code for issues, or get feedback on implementation. Covers correctness, security, performance, readability, and best practices across languages.

The English summary is being prepared. Showing the original description.

Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.

The English summary is being prepared. Showing the original description.

上线前 PR 审查。分析当前分支与基础分支的 diff，检查 SQL 安全、竞态条件、 LLM 信任边界、枚举完整性等测试捕获不到的结构性问题。发现问题直接修复。 触发方式：用户说"review"、"审查代码"、"上线前检查"、"forge-review"，或 forge-dev --full 调度。 与内置 code-review/verify 的分工：forge 工作流内的上线前结构性审查用本 skill；用户点名 /code-review 或 /verify 时用对应内置 skill。

The English summary is being prepared. Showing the original description.

GitHub PRのレビューコメントを自動検出し、コード修正を適用する。インラインスレッド・レビュー本文・Issueコメントに対応し、CodeRabbit・Copilot等のbotコメントも処理する。PRレビュー後の修正作業を自動化したい場合に使用する。Do NOT use for レビュー自体の実施（ai-code-reviewを使用すること）。

The English summary is being prepared. Showing the original description.

ローカルの変更差分（git diff）を3つのサブエージェントで並列レビューし、結果を統合して修正を適用する。PR作成前やタスク完了前のローカル品質チェックに使用する。ai-code-reviewと同一の6観点・重大度基準を適用する。

The English summary is being prepared. Showing the original description.

コード・設計・指示のレビュー依頼で、対象と観点を確定し、観点ごとに独立した評価者へ配分して結果を統合する。割り当てられた観点の評価担当はcode-review-guidanceを使う。

The English summary is being prepared. Showing the original description.

Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding

The English summary is being prepared. Showing the original description.

コード品質の最終確認。Skill: code-review (built-in) で correctness bug を検出 → main agent が findings を修正 → lint/ty 静的解析 → 条件付きで security-reviewer / critic を spawn (security 関連変更 or plan/requirements.md がある時のみ)。「品質チェックして」「品質ゲート通して」「レビューして」「コードを確認して」「PR 出す前にチェック」「セキュリティ大丈夫？」「コード見て」で発動。

The English summary is being prepared. Showing the original description.

Design AI-powered code review systems. TRIGGERS - Use when user needs help with ai-code-review-system related tasks.

The English summary is being prepared. Showing the original description.

PR レビュー。PR 番号・URL・ブランチ名・Slack リンク等を添えて PR の「レビュー」を依頼された時に使用（ビルトインの /review ではなく本スキル）。Claude Code と外部 CLI のマルチモデルレビューで Critical/High/Medium の指摘を報告する。境界: ローカル未コミット変更は /code-review、自ブランチの提出前チェックは self-review、特定コメントへの対応は pr-comment。PR の状態確認・作成相談では使わない。

The English summary is being prepared. Showing the original description.

Uncorrelated Evaluator — 4軸ルーブリック専門エージェント（functionality-reviewer・code-reviewer・design-reviewer・originality-reviewer）と security-reviewer を5並列実行し、成果物を多面的に独立評価します。PASS / NEEDS WORK / BLOCKED 判定を返します。Self-leniency 防止のため、実装エージェントのコンテキストを引き継がない新規エージェントとして起動します。「レビューして」「評価して」「実装を確認して」などのリクエストで起動します。

The English summary is being prepared. Showing the original description.

Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.

The English summary is being prepared. Showing the original description.

このブランチ、またはこのセッションで書いた差分の全体を読み直し、用語の揺れ・古いまま残ったコメント・追従し損ねた実装 (呼び出し元・対になる箇所・テスト・文書) を探して、裏の取れたものを直す。「差分全体を見直して」「用語の揺れや更新漏れが無いか見て」「refresh-on-session」「/refresh-on-session」で発火。バグ探しは code-review、ディレクトリの文書と実体の一括照合は claude-md-refresh、issue 本文の書き戻しは issue-writeback の担当。

The English summary is being prepared. Showing the original description.

Review code changes from current branch, an Azure DevOps PR, a git ref, or a diff/patch file. Trigger when user says "review this", "code review", "/df:code-review", or provides a PR id/URL, ticket URL, git ref, or diff path. Read-only — never posts comments.

The English summary is being prepared. Showing the original description.

Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.

The English summary is being prepared. Showing the original description.

Pre-commit review: security scan, quality gates, auto-fix.

The English summary is being prepared. Showing the original description.

Review PRs: diffs, inline comments via gh or REST.

The English summary is being prepared. Showing the original description.

Pre-PR code review checklist for this repo. Plan alignment, security gates, layering, dead code, API-surface completeness. Used by the code-reviewer agent.

The English summary is being prepared. Showing the original description.

Evaluate code review feedback against the actual code, supported environments, and existing behavior. Clarify uncertain requests, respond with technical evidence, and implement valid changes one at a time with tests for each fix.

• Clarifying ambiguous code review comments
• Checking whether suggested changes preserve compatibility
• Assessing whether a requested feature is actually used

Turn a specification and its tickets into code by coordinating multiple agents around task dependencies. Combine their work on one integration branch, use test-driven development, review the result, and close tickets through the issue tracker’s workflow.

• Implementing a specification with multiple tickets
• Working on independent tickets in parallel
• Combining implementations on one integration branch

Build features or fix bugs by writing one failing test, then the smallest implementation that passes it. Tests check behavior through public interfaces, the entry points callers use, so they remain useful when internal code changes.

• Building a feature one test at a time
• Fixing a bug with a failing test first
• Planning integration tests at agreed public interfaces

Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.

• Reviewing changes on a branch or pull request
• Checking changes since a chosen commit or tag
• Checking compliance with documented coding standards