메뉴
Run a comprehensive code review of local changes, analyzing staged and unstaged changes to provide insights, identify issues, and suggest alternative approaches. Use when reviewing code before committing or creating pull requests.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | code-review |
| description | Run a comprehensive code review of local changes, analyzing staged and unstaged changes to provide insights, identify issues, and suggest alternative approaches. Use when reviewing code before committing or creating pull requests. |
Run a comprehensive, critical code review of local changes. This skill analyzes staged and unstaged changes to provide insights, identify issues, and suggest alternative approaches.
When this skill is invoked:
.claude/agents/code-review/instructions.md/code-review # Review all uncommitted changes
/code-review --staged # Review only staged changes
/code-review <commit> # Review changes in a specific commit
/code-review <base>..<head> # Review changes between commits
Based on arguments:
git diff HEAD (all uncommitted changes)--staged: git diff --staged<commit>: git show <commit><base>..<head>: git diff <base>..<head>For each modified file:
Apply the review framework from .claude/agents/code-review/instructions.md:
For non-trivial changes, brainstorm alternative approaches:
Inspect the diff for user-facing changes — public API renames or signature changes, behavior changes, schema/migration changes, user-visible bug fixes, breaking changes. If any are present, confirm a .changeset/*.md entry exists that:
patch / minor / major).major and includes migration guidance.Treat a missing changeset as a CRITICAL issue when the diff has user-facing changes. Internal-only changes (refactors with no API impact, tests, types-only tightening, doc-only edits, build/CI/tooling, benchmarks, examples) do not need a changeset.
Provide a structured report with:
# Code Review: [brief description of changes]
## Summary
[2-3 sentence overview of what the changes do and overall assessment]
## Critical Issues
[Issues that would cause bugs, security vulnerabilities, or data loss]
## Concerns
[Design issues, edge cases, potential problems]
## Suggestions
[Improvements, style, minor issues]
## Alternative Approaches
### Alternative 1: [Name]
**Approach:** [Description]
**Trade-offs:**
- Pro: ...
- Con: ...
**When to prefer:** [Conditions where this is better]
### Alternative 2: [Name]
...
## Questions
[Clarifying questions for the author about intent or requirements]
Run a comprehensive review of the Queuert library before publishing, launching 10 parallel agents to check documentation coherence, API design, implementation verification, feature completeness, API consistency, schema design, code style, benchmarks, changeset coverage, and OTEL semantic conventions. Use when preparing to publish or validating publish readiness.
Create a release for the Queuert monorepo. Guides through changeset creation, version bumping, committing, merging dev to main, tagging, and creating a GitHub prerelease.
Check if documentation is up to date with code changes. Analyzes git changes and identifies documentation that may need updating, comparing code modifications against reference docs and package READMEs.
Generate a conventional commit message from staged changes. Analyzes changes to determine affected packages and appropriate commit type, then outputs a properly formatted commit message.
Identify flaky tests by running tests multiple times and analyzing intermittent failures. Use when investigating test reliability.