菜单
Use when the user says "review the code", "check these changes", "review this", "look at staged changes", or invokes /code-review. Also invoked automatically by git-commit skills if no review has been done this session. Applies to Java/Quarkus, TypeScript, and Python projects.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mdproctor/cc-praxis --skill code-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Use when the user says "bump a version", "upgrade dependencies", "check for newer versions", "add a dependency", or "run audit" — for Java/Maven, TypeScript/npm, or Python/pip projects. Routes to the correct package manager based on project type declared in CLAUDE.md.
Use when user wants to create a commit NOW — says "commit this", "commit these changes", "create a commit". Routes to Java or custom project workflows when CLAUDE.md declares those types; falls back to generic commit for all others. Does NOT apply to discussions about past commits or questions about whether to commit.
Use when the commit history contains noise — fixup commits, revert chains, docs wording chores, tiny cleanups — that obscures meaningful history. Also triggered when the pre-push hook flags squash candidates, or invoked on demand via /git-squash on any commit range.
| name | code-review |
| description | Use when the user says "review the code", "check these changes", "review this", "look at staged changes", or invokes /code-review. Also invoked automatically by git-commit skills if no review has been done this session. Applies to Java/Quarkus, TypeScript, and Python projects. |
Reads the project type, then loads the appropriate language-specific review checklist. Universal review principles apply to all types.
Load ~/.hortora/garden/approaches/code-review.md before proceeding.
All review severity models, reporting formats, and workflow steps are defined there.
python3 ~/.claude/skills/project-init/ctx.py
Read PROJECT_TYPE from the output.
Extract: java | ts | python | generic
If type is missing or generic, inspect staged files:
.java files or pom.xml changed → treat as java.ts / .tsx files changed → treat as ts.py files changed → treat as python| Project type | File to read |
|---|---|
java | ~/.claude/skills/code-review/java.md |
ts | ~/.claude/skills/code-review/typescript.md |
python | ~/.claude/skills/code-review/python.md |
Read the file, then execute the review workflow it describes.
Invoked by: [java-dev], [ts-dev], [python-dev] before committing; [java-git-commit] when no review has been run this session
Invokes: [security-audit] for auth/payment/PII code (offered, not automatic); [git-commit] after approval if user wants to commit