メニュー
Review given file/dir/repo for current-state code organization: module boundaries, design patterns, cross-module dependencies, tech debt, and interface stability. Scope-only atomic skill; output is a findings list.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | review-codebase |
| description | Review given file/dir/repo for current-state code organization: module boundaries, design patterns, cross-module dependencies, tech debt, and interface stability. Scope-only atomic skill; output is a findings list. |
| description_zh | 对给定路径（文件 / 目录 / 仓库）做 scope-only 原子审查，覆盖模块边界、模式一致性、跨模块依赖、技术债与接口稳定性。 |
| tags | ["code-review","scope-only"] |
| license | MIT |
| recommended_scope | project |
| metadata | {"author":"ai-cortex"} |
| triggers | ["review codebase","codebase review"] |
| input_schema | {"type":"code-scope","description":"Files, directories, or repository path to review for current-state structure"} |
| output_schema | {"type":"findings-list","description":"Findings on module boundaries, patterns, dependencies, tech debt, and interface stability"} |
对给定路径（单文件 / 目录 / 仓库）的当前状态做 scope-only 原子审查。与 review-diff（仅审查 git 变更）成对作为 orchestrate-code-review 的 scope 步候选——本技能看快照，review-diff 看变更。
不做：安全 / 性能 / 架构等 cognitive 维度（由 cognitive 步的原子技能 review-security / review-performance / review-architecture 承接），也不做语言或框架特定分析（由 language / framework 步承接）。
首要目标：产出 scope-only findings list，识别给定路径的结构性问题（边界、模式、依赖、技术债、接口）。
成功标准（必须全部满足）：
file:line 引用scope）/ severity / title / description / suggestion本技能负责：
本技能不负责：
review-diff）orchestrate-code-review）review-<lang> / review-<framework>）review-security / review-performance / review-architecture）交接点：findings 输出后，作为 orchestrate-code-review 的 scope 步聚合输入；或交给用户决定后续（重构 / 进一步深审）。
src/auth/ 看当前结构与依赖review-diff 二选一| 项目 | 默认 | 用户偏离方式 |
|---|---|---|
| 路径 | 仓库根 | 选择：[仓库根] / [当前文件目录] / [列出顶级目录选择] |
| 大范围处理 | 按层（模块 / 目录）输出 | 选择优先子集（从顶级目录列表选） |
运行前必须确认两件事：(1) 审查路径；(2) 大范围时按层 vs 优先子集。
对范围内代码（按用户选定的层 / 子集），输出以下维度的 findings：
每条 finding 必须含 file:line 引用。
如果在分析中发现属于安全 / 性能 / 架构 / 语言 / 框架的具体问题：标记并提示对应原子技能，但不展开分析。例：
检测到潜在 SQL 注入风险（user input 未转义直接拼接），建议运行
review-security
file:line 引用的 finding不做（其他原子技能负责）：
review-difforchestrate-code-reviewreview-<lang>review-<framework>review-security / review-performance / review-architecturesrc/auth/auth.go:42 类引用；遇到加密弱算法仅标记并提示 review-securitypkg/validator/validator.goStore, look up, or delete a personal credential (server SSH password, database password, website login, API key/token, certificate passphrase) in the macOS Keychain using a consistent <project>-<env>-<kind> naming scheme, and optionally record a pointer (never the secret itself) in the current project's Claude Code memory. Always use this skill whenever the user asks to save, store, remember, look up, rotate, or delete a password, API key, token, SSH credential, or database credential on this machine — even if they don't say "Keychain" or "security" explicitly, e.g. "save this database password so I don't lose it", "把这个数据库密码存一下", "记一条密钥", "这台服务器的密码帮我记下来", "what's the postgres password for staging again", "delete the old GitHub token from keychain". Do not use this for team-shared secret vaults, CI/CD secret injection, or anything that needs to sync across machines — those need a real secrets manager, not this skill.
Drain pending NATS messages from a producer contract via NATS MCP tools. Discovers the available NATS tool capabilities, selects exact-subject or wildcard mode from .cortex/nats.yaml, applies Tolerant Reader semantics, executes ack/nak/term decisions, and returns aggregated stats.
Audit and refactor existing SKILLs to meet spec compliance, repository asset boundaries, tool adaptation requirements, and LLM best practices.
From inside a linked worktree, deliver the current feature branch into main — merge with --no-ff, push, and optionally clean up the worktree, all without leaving CWD.
After code changes, auto-detect the project's build system and local deployment method for a given directory, then build the project and restart its locally-deployed environment (Docker Compose / systemd / process manager). Never assumes — asks only when detection is ambiguous. Caches detected commands per project in .cortex/redeploy-local.yaml; re-invocations on the same project skip re-scanning until signal files change, the cache expires (30 days), or the skill version bumps.
From the main repo on the main branch, scan all linked worktrees and local branches, let the user multi-select, then merge --no-ff + push them sequentially and clean up succeeded worktrees together.