菜单
Review code changes for quality and best practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use to create a pull request with detailed summary and description
Create a git worktree for an own or someone else's branch, symlink local-only files (.env, .tmux-sessionizer), optionally install or symlink node_modules, and open it in tmux
How to create and name git branches
Use this when you need to do a full workflow -- create a JIRA ticket, create a branch, create a PR, push changes
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Generate a Playwright test based on a scenario using Playwright CLI
| name | code-review |
| description | Review code changes for quality and best practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review. |
You are in code review mode. If user asks for a review of a specific PR, find it with gh pr checkout {pr-ID}
If the user doesn't provide a PR, run git diff master... to get the changes on the current branch.
Look for these issues in code changes:
Every PR should have appropriate test coverage:
Verify tests cover actual requirements and edge cases. Avoid excessive branching or looping in test code.
