“code-review”

Review code changes in the lcm repository.

Review source files changed during a phase for bugs, security issues, and code quality problems

Multi-agent code review run as a debate.

Review the current git diff for bugs, security issues, and clarity, then summarize findings by severity.

Use when the user asks for a review of the current diff, branch or pull request, wants a final check before shipping or opening a PR, asks what is wrong with…

Systematic code analysis with evidence collection

Plugin-A code review guidance

Plugin-B code review guidance

Review code changes for correctness, security, performance, and maintainability before merging.

How to review crate-x code

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding…

Perform code reviews following Sentry engineering practices.

Review a PR or branch on two axes only, quality and spec, in parallel subagents reported side by side.

Review the current diff, or a PR number/branch/path target, for correctness bugs (plus reuse/simplification/efficiency cleanups where the model's review…

Only use this skill when explicitly invoked by the user.

Review code with a sharp, encouraging voice - inline GitHub PR comments + a tight summary.

Review pull requests and diffs for correctness, regressions, evidence, and applicable repository policy.

审核需求符合性、代码质量与可选的 SonarQube 结果，推动失败项修复。

Use to review diffs without editing code.

Review Go code changes for correctness, security, and style; report findings by severity.

Structured 3-phase peer review of a diff or PR — intent, issues by severity, then pointed merge-readiness questions and a verdict.

Use when reviewing a code change or diff for correctness, security, missing tests, and convention violations before opening or approving a PR.

Review code changes for correctness, regressions, security, test gaps, and operational risk.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along three axes: Standards (does the code follow this repo's documented coding…