菜单
Review code for bugs, security vulnerabilities, performance issues, and maintainability. Use when the user says "review this code", "check this PR", "look at this diff", or "is this code safe?", or shares code and asks for feedback.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
MANUAL skill covering the full atlas lifecycle outside of task work: onboard (scaffold the docs/ SSOT plus .atlas/ internal state, inventory skills, recommend what to run next), install (verify and wire claude-mem, context-mode, hooks, project config), connectors (guided vendor MCP connector setup across domain plugins), and repair (fix a broken atlas install: marketplace, rollbacks, hooks, assets). Run with no args for onboarding plus recommendations; run with --fix to auto-repair.
Atlas architect: boot the workspace. Verify claude-mem and context-mode, scan the project, recommend tooling (confirm first), wire hooks, seed the docs/ SSOT.
This skill should be used when the user asks to "audit my codebase against The Pragmatic Programmer", run a "pragmatic audit", "check what pragmatic principles are implemented", "review codebase for pragmatic practices", "find what's missing from the pragmatic programmer in this project", or wants a structured review of a codebase/project/monorepo against the book's principles, tips, and practices. Produces a ranked report of what is implemented, partially implemented, and missing, each finding cited to the book concept and to file:line evidence. Supports --chapters to scope dimensions and --report to set output path.
This skill should be used when the user is "designing a module", "deciding an architecture", "debugging a bug", "refactoring code", "writing tests", "naming things", "handling concurrency", "decoupling components", "choosing inheritance vs composition", "adding error handling", asks "what does The Pragmatic Programmer say about X", "is this DRY", "should I use inheritance or composition", "how should I structure this", or otherwise wants the relevant Pragmatic Programmer principles, tips, or practices surfaced for the work in progress. Surfaces 1-4 relevant principles with book tip numbers and citations to the concept files.
Create or modify a reusable component that survives latency, cancellation, and partial failure (progress modal, upload widget, job panel), handling every backend state with all six interaction states rendered.
Read-only database audit via parallel subagents: inventory a live schema, reconcile it against the code, and check privileges and naming before any change.
| name | code-review |
| description | Review code for bugs, security vulnerabilities, performance issues, and maintainability. Use when the user says "review this code", "check this PR", "look at this diff", or "is this code safe?", or shares code and asks for feedback. |
| when_to_use | When reviewing a diff, PR, files, or pasted code for security, performance, correctness, or maintainability findings with file and line references |
| allowed-tools | Read, Glob, Grep, Bash |
Structured code review covering security, performance, correctness, and maintainability. Works on diffs, PRs, files, or pasted code snippets.
Read the diff once to learn what changed and why, before grading it. Then pick the review dimensions that match the change surface: a SQL change leans on Security and Performance; a refactor leans on Maintainability and Correctness. Do not apply every checklist to every diff.
The full per-dimension checklists and how to apply them live in
references/review-checklists.md. Read the section for the dimension
you are reviewing; do not apply every item to every diff.
Rate each reviewed dimension and provide specific, actionable findings with file and line references. Prioritize critical issues first, then minor, then positives. Always include positive observations alongside issues so the author sees what to keep.
