用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/asermax/claude-plugins --skill review-code命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Build something already designed, together with the user, then verify it and offer to commit. Use when a design is agreed and the work is ready to write, or when another skill needs the shared build discipline.
Load first when working with any zenku skill. Carries the vocabulary, the two rules, how to find the project's vault and conventions, and the habits for writing into it.
Lay out the current shape so the user can settle a new one — which modules exist, where the seams are, how data flows, and what earlier quests already decided. Use when the user wants to design a feature or a module, work out an interface, decide where a boundary belongs, or when another skill needs a shape agreed before code.
基于 SOC 职业分类
正在显示 SKILL.md
| name | review-code |
| description | Review code against specs, designs, and decision compliance |
| argument-hint | [context] |
| disable-model-invocation | true |
Review code for spec compliance and pattern adherence.
Context: $ARGUMENTS (optional - can be: branch, files, or description)
You must load the following skills and read the following files before proceeding.
katachi:framework-core - Workflow principlesdocs/architecture/README.md - Architecture decisions (ADRs)docs/design/README.md - Design patterns (DES)Read relevant docs/feature-specs/ and docs/feature-designs/ based on code being reviewed.
Based on input, determine what to review:
If branch specified:
git diff main...$BRANCH
If files specified:
If description specified:
If no input:
For the code being reviewed:
If documentation can't be identified:
"I see changes in [files]. Which feature is this for?
Or should I do a general code review without spec reference?"
Task(
subagent_type="katachi:code-reviewer",
prompt=f"""
Review this code.
## Code to Review
{code_content}
## Feature Spec (if applicable)
{spec_content or "No spec identified"}
## Feature Design (if applicable)
{design_content or "No design identified"}
## Relevant ADRs
{adr_content}
## Relevant DES Patterns
{des_content}
"""
)
Show review results organized by severity:
## Code Review Results
### Critical Issues
- [Issue]: [location] - [recommendation]
### Important Issues
- [Issue]: [location] - [recommendation]
### Suggestions
- [Suggestion]
### Pattern Compliance
- ADR-007 (logging): Compliant
- DES-003 (testing): Violation at tests/test_x.py:45
### Strengths
- [What's done well]
For each issue:
Ask: "Would you like me to help fix any of these issues?"
If user wants fixes:
This is a review process: