菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
Use when ending a mid-work session (branch stays open) and wanting to preserve context for resumption, OR when a session is beginning and needing to resume from where things left off — says "create a handover", "end of session", "update the handover", "write a handover", "wrap", or "resume handover". NOT for branch closure (use work-end — it includes the full wrap). NOT for project narrative (use write-content, diary type).
Use when setting up GitHub issue tracking, planning implementation work (creating epics and child issues from a plan), when a user request spans multiple concerns that should be separate issues, or when staged changes span multiple issues and should be split. Also invoked automatically throughout the development lifecycle when Work Tracking is enabled in CLAUDE.md.
Use when correctness, completeness, or consistency of a project needs verification — "is the project healthy?", "pre-release check", "do a health check", "check docs are in sync", invokes /project-health. NOT for improvement suggestions (use project-refine for that).
| 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