“code review”

Structured engineering code review covering readability, complexity, test gaps, SOLID principles, and API consistency.

Review a branch, PR, or worktree diff for repository conventions and stated intent.

Review diffs and change sets for bugs, regressions, risks, and missing tests.

How to review crate-x code

Reviews this session's code against the criteria in review-code.md.

Review code for bugs, security issues, and style violations.

Review code changes and report concrete risks first.

Reviews code for correctness, security, performance, and project standards using independent review passes.

Expert code review against architecture and coding standards: readability, maintainability, security, performance, layering, Sonar-equivalent cleanliness…

Review code changes or repositories for correctness, security, performance, architecture, maintainability, dead code, unnecessary complexity, and technical…

Provides a structured workflow for planning and executing code reviews like a senior engineer.

Review code changes against project coding standards and specification requirements.

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

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

conducts a code review

Automated code review for pull requests using specialized review patterns.

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

Aplicar code review cuando el encargo requiera diff, intención y pruebas.

Conduct evidence-based code reviews of files, diffs, pull requests, or working changes using independent general, architectural, and language perspectives.

Conducts multi-axis code review.

Use this skill when the user asks for a code review, audit, inspection, sanity check, or independent verification of existing code or changes, such as a pull…

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…

Review code changes for correctness, regressions, and missing validation when asked to review a patch or pull request.

Review code changes with several independent reviewers in parallel, then triage and present the findings.