メニュー
Review code changes for quality, security, performance, and maintainability. Use when reviewing PRs, diffs, or code files. Provides structured feedback with severity levels.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use bearcli to safely read, search, edit, tag, archive, and organize Bear.app notes. Use when working with Bear notes, note IDs, Bear tags, migrations from Obsidian, note cleanup, or personal knowledge management in Bear.
Use rn-logs to read React Native Metro logs via CDP without MCP overhead. Default output is plain text and safe for non-interactive agent runs.
Automate iOS Simulator using AXe CLI. Use after implementing features to verify they work correctly via UI automation.
Create well-formatted git commits using Conventional Commits format. Use when committing changes, reviewing commit messages, or splitting changes into atomic commits.
Fetch source code for npm packages, Python packages, Rust crates, or GitHub repos to understand their implementation. Use when you need to explore a library's internals.
This skill should be used when users need to interact with GitHub via the gh CLI. It covers repository management (create, delete, clone, fork), CI/CD workflows (GitHub Actions), Issues, Pull Requests, Releases, and other GitHub operations. Triggers on requests mentioning GitHub, repos, PRs, issues, actions, or workflows.
| name | code-review |
| description | Review code changes for quality, security, performance, and maintainability. Use when reviewing PRs, diffs, or code files. Provides structured feedback with severity levels. |
Review code to improve overall codebase health while enabling developer progress.
Approve changes that improve code health, even if imperfect. No "perfect" code exists—seek continuous improvement. Don't block PRs for nitpicks.
Use these prefixes in feedback:
[Critical] — Must fix before merge (security, bugs, data loss)[Important] — Should fix, can discuss (perf, design, complexity)[Nit] — Nice to have, author can ignore (style, polish)Structure feedback as:
## Summary
[1-2 sentence overall assessment]
## Critical Issues
- [Issue with explanation and suggested fix]
## Important Suggestions
- [Issue with explanation]
## Nits
- [Optional polish items]
## Good Patterns
- [Acknowledge what was done well]