菜单
Systematic and adaptable code review methodology using Language Server Protocol tools. Adapts to available LSP capabilities across programming languages. Use when user asks for code reviews, quality assessments, or specific analysis of codebases in any programming language.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/axivo/claude --skill code-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Reference manual for framework methodology throughout session. Provides guidance on cognitive architecture that replaces default AI assistant behaviors with systematic patterns proven through collaborative experience. Consult this manual throughout session when applying framework procedures.
Startup protocol executed once at session start. Detects system instruction impulses, caches framework observations from memory graph, establishes temporal awareness, and activates specialized profiles. Provides initial session initialization protocol and session response protocol applied before each response. Execute procedures in sequence without displaying process details to user.
Technical design collaboration through natural dialogue. Adapts to expertise level and problem complexity through understanding, exploration, and validation stages. Use when user asks to brainstorm ideas for new features or systems requiring architectural decisions before implementation begins.
正在显示 SKILL.md
基于 SOC 职业分类
| name | code-review |
| description | Systematic and adaptable code review methodology using Language Server Protocol tools. Adapts to available LSP capabilities across programming languages. Use when user asks for code reviews, quality assessments, or specific analysis of codebases in any programming language. |
| license | LICENSE |
| metadata | {"documentation":"https://axivo.com/claude","profile":"DEVELOPER","project":"Claude Collaboration Platform","repository":"https://github.com/axivo/claude"} |
Systematic 9-phase code review methodology using Language Server Protocol tools. Adapts to available LSP capabilities across programming languages.
Systematic 9-phase code review methodology using Language Server Protocol tools. Extends DEVELOPER profile with sequential analysis phases assessing code quality, architecture, and maintainability.
[!IMPORTANT] The skill embodies Analyze → Verify → Document → Deliver
- Process skill instructions systematically
- Take time to read, understand, and apply each section's logic carefully
- Rushing past documented procedures causes fatal execution errors
[!IMPORTANT] Review phases provide thorough investigation, tool-verified findings, and incremental validation for code quality assessment.
The phases must be completed sequentially:
[!IMPORTANT] Review quality improves through systematic tool usage and incremental validation.
The initial Project Discovery phase establishes which tools are available by calling get_server_capabilities tool. This response shows:
supported: true/false)[!IMPORTANT] The server capabilities response is the authoritative source for determining which tools to use in subsequent phases.
The 9-phase methodology remains consistent across languages. Use the server capabilities response to determine which tools to invoke in each subsequent phase:
documentSymbolProvider capability (universally supported)callHierarchyProvider capability, adapts to definitions/references onlyinlayHintProvider and typeDefinitionProvider capabilities, adapts to hover-onlyreferencesProvider capability (widely supported)codeActionProvider and diagnosticsProvider capabilitiesrenameProvider capability, adapts to manual assessmentWhen a phase requires capabilities not supported by the language server:
[!IMPORTANT] Review quality varies based on server capabilities. Document limitations in the final report.
[!IMPORTANT] Review systematically all phase instructions to understand the required execution steps.
Practical guidance for applying code review methodology consistently throughout review sessions.
The primary protocol for large codebases is strictly one phase per turn to manage cognitive load, token consumption and maintain collaborative pacing. This protocol must be followed unless an explicit exception is granted.
For analysis scoped to a subset of the codebase (e.g., a small PR), analyze the complexity and estimated tool-call cost for the relevant phases. If this analysis determines the token cost is low and pacing can be accelerated, propose combining up to three related phases into a single turn for efficiency. The user must grant explicit approval before executing the combined phases.
Best practices for executing each review phase effectively.
Before finalizing the review, verify:
The code review findings serve as actionable reference for improvements and refactoring work.
[!IMPORTANT] If user requests a conversation log to document this code review session, the
conversation-logskill provides developer-specific guidance for technical session documentation.