Decide Fit First

• Core job: 本技能提供专业的代码审查能力，帮助发现潜在问题并提供改进建议。 1. 代码质量 可读性: 命名规范、注释完整性、代码结构 可维护性: 模块化程度、耦合度、复杂度 一致性: 代码风格、设计模式使用 2. 潜在问题 Bug 风险: 空指针、边界条件、异常处理…
• Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
• Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

• Structure: The skill is organized around “审查维度”, “1. 代码质量”, “2. 潜在问题”, “3. 最佳实践”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
• Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
• Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

• Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
• Invocation: Name code-review directly; if the source includes slash commands, start with the command and then add task context.
• Validation: Start small and check whether the result follows “审查维度 / 1. 代码质量 / 2. 潜在问题” before expanding.

Boundaries And Review

• Dependencies: It usually needs no extra API key, so start with a small validation task.
• Permissions: Declared permissions include read; ask the agent to state file, command, and rollback boundaries before acting.
• Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.