Code Review Service

v1.0.0

提供全面代码审查,涵盖功能、可读性、性能、安全性和可维护性,生成详细改进报告提升代码质量。

0· 122·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for yang1002378395-cmyk/code-review-service.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Code Review Service" (yang1002378395-cmyk/code-review-service) from ClawHub.
Skill page: https://clawhub.ai/yang1002378395-cmyk/code-review-service
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install code-review-service

ClawHub CLI

Package manager switcher

npx clawhub@latest install code-review-service
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description align with SKILL.md content: step-by-step guidance for functional/readability/performance/security/maintainability reviews and report templates. References to SonarQube/ESLint/GitHub/GitLab are reasonable for a code-review workflow.
Instruction Scope
SKILL.md stays within code-review scope (checklists, report templates, communication tips). It suggests using external analysis tools and repository review workflows but does not itself instruct the agent to fetch files, read system paths, or exfiltrate data. Minor ambiguity: automated use of SonarQube/ESLint or MR review implies repo/tool access (not described), so explicit access/credential steps would be needed for automation.
Install Mechanism
No install spec and no code files — instruction-only, nothing is written to disk and no external packages are fetched by the skill itself.
Credentials
No required environment variables, credentials, or config paths are declared. This is proportional for a guidance-only skill. If you later integrate it with CI/tools you will need to supply appropriate tokens — those are not requested by the skill.
Persistence & Privilege
always is false and the skill is user-invocable only; it does not request permanent elevated privileges or write to other skills' configs.
Assessment
This skill is an instruction-only code-review template and appears coherent with its purpose. Points to consider before installing or using it in automated workflows: - Source is unknown (no homepage); prefer skills from known maintainers when possible. - The skill itself requests no credentials, but following its advice (running SonarQube, ESLint, or performing MR reviews) will require access tokens and repository read access — grant those minimally (read-only, scoped service accounts) and avoid reusing admin credentials. - If you plan to let an agent automatically fetch repositories or run analysis tools, isolate that capability (dedicated service account, limited permissions) and review logs/outputs for leaked secrets. - Review generated reports before sharing externally — code reviews can inadvertently include sensitive snippets (API keys, internal URLs). - Because this is guidance-only (no code/install), the direct risk from the skill is low; the primary risk comes from how you connect it to your code and tools. Ensure standard operational precautions when integrating with CI/CD or repo hosting.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d4dvch4m85w3q2w8739y5zx83s1hv
122downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Skill: 代码审查服务助手

触发词

  • Code Review
  • 代码审查
  • 代码评审
  • 代码质量

使用场景

用户想提供代码审查服务,帮助其他开发者提升代码质量。

核心框架

代码审查维度

  1. 功能性 - 代码是否正确实现需求
  2. 可读性 - 代码是否易于理解
  3. 性能 - 代码是否高效
  4. 安全性 - 代码是否有漏洞
  5. 可维护性 - 代码是否易于维护

执行步骤

1. 审查准备

获取信息

  • 项目背景
  • 技术栈
  • 业务需求
  • 重点审查方向

工具准备

  • SonarQube(静态分析)
  • ESLint/Prettier(代码风格)
  • GitLab/GitHub MR Review

2. 审查维度

结构审查

✅ 目录结构是否清晰
✅ 模块划分是否合理
✅ 命名是否规范
✅ 是否有重复代码

代码审查

✅ 函数是否过长(< 50 行)
✅ 参数是否过多(< 5 个)
✅ 是否有嵌套地狱(< 3 层)
✅ 是否有魔法数字
✅ 错误处理是否完善
✅ 日志是否合理

性能审查

✅ 是否有 N+1 查询
✅ 是否有不必要的循环
✅ 是否有内存泄漏风险
✅ 是否有阻塞操作

安全审查

✅ SQL 注入风险
✅ XSS 攻击风险
✅ CSRF 防护
✅ 敏感数据加密
✅ 权限校验

3. 审查报告模板

# 代码审查报告

**项目**:[项目名称]
**审查范围**:[文件/模块]
**审查日期**:[日期]
**审查人**:[姓名]

## 总体评价
- 代码质量:⭐⭐⭐⭐☆(4/5)
- 主要问题:[数量] 个
- 建议改进:[数量] 条

## 发现的问题

### 🔴 严重问题(必须修复)

#### 1. [问题标题]
- **位置**:[文件:行号]
- **问题描述**:[描述]
- **影响**:[影响]
- **建议修复**:[修复方案]

### 🟡 一般问题(建议修复)

#### 1. [问题标题]
- **位置**:[文件:行号]
- **问题描述**:[描述]
- **建议修复**:[修复方案]

### 🟢 优化建议(可选改进)

#### 1. [建议标题]
- **位置**:[文件:行号]
- **当前实现**:[当前代码]
- **建议改进**:[改进代码]

## 亮点
- [亮点 1]
- [亮点 2]

## 总结
[总结评价]

4. 沟通技巧

提出问题

  • ❌ "这代码写得不好"(攻击性)
  • ✅ "这里可能会有性能问题,建议优化为..."(建设性)

解释原因

  • ❌ "改成这样"(命令式)
  • ✅ "这样修改可以提升 50% 性能,因为..."(解释原因)

尊重作者

  • ❌ "你犯了个错误"
  • ✅ "我发现了一个潜在问题"

5. 定价参考

服务类型价格交付物
单文件审查¥49/文件审查报告
模块审查¥199/模块审查报告 + 改进建议
项目审查¥999-2999/项目完整审查报告 + 架构建议
持续审查¥1999/月月度审查 + 培训

6. 变现渠道

平台接单

  • Fiverr(海外)
  • 猪八戒(国内)
  • 码市(国内)

内容引流

  • 掘金/知乎文章
  • GitHub 开源
  • 技术社群

企业服务

  • 代码审查外包
  • 技术培训
  • 质量体系建设

输出格式

🔍 代码审查服务方案

审查范围:[范围]
预计时间:[X] 小时
定价:¥[Y]

审查维度:
- [x] 功能性
- [x] 可读性
- [x] 性能
- [x] 安全性
- [x] 可维护性

交付物:
- 审查报告
- 问题清单
- 改进建议

定价建议

  • 免费基础审查(单文件)
  • 深度审查:¥199-999
  • 企业级服务:¥1999-9999

Comments

Loading comments...