菜单
Review staged git changes for bugs, style issues, and best practices. Use when the user asks for a code review or CR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit local Docker images and running containers for hardening issues before deploy — privileged flags, root users, stale base images, missing resource limits. Use for pre-deploy container review.
Check system health before deploying. Verifies disk space, memory, and running services to catch issues before they hit production.
Automatically format code after edits. Runs prettier/black on modified files to keep style consistent.
Review staged git changes for bugs, style issues, and best practices. Use when the user asks for a code review or CR.
Set up a project for development. Install dependencies, configure environment, and verify the setup works. Use when the user asks to set up, install deps, or get started with a project.
Check project dependencies for license compliance issues. Use when the user asks about licenses, compliance, or legal review of deps.
| name | review-staged |
| description | Review staged git changes for bugs, style issues, and best practices. Use when the user asks for a code review or CR. |
Review the currently staged git changes and provide actionable feedback.
git diff --staged to see what's being committedgit diff to review unstaged changesWhen checking style and readability, refer to the project's coding
standards documented in ${CLAUDE_SKILL_DIR}/review-guidelines.md.
Provide your review as a structured list:
List any bugs, security problems, or correctness issues that MUST be fixed.
List style, readability, and minor improvement suggestions.
A one-line overall assessment (e.g., "Looks good with minor nits" or "Has a critical SQL injection — do not merge").
Keep feedback specific and actionable. Reference exact line numbers from the diff. Be concise — developers don't want a wall of text.