home / skills / cacr92 / wereply / code-review

code-review skill

safe

This skill helps you review code for Rust, React, and databases, identifying risks, regressions, and incorrect typings to improve reliability.

npx playbooks add skill cacr92/wereply --skill code-review

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.3 KB

---
name: code-review
description: 当用户要求代码审查、Review、找风险或列问题时使用。
---

# Code Review Skill

## 适用范围
- Rust/Tauri 后端审查
- React 前端审查
- 数据库与性能风险检查

## 关键规则（Critical Rules）
- 优先发现逻辑错误与回归风险
- 检查命令签名与类型导出是否完整
- 检查前端是否违反 `console.*` / `as any`
- UI 表格：检查表格行高/内边距是否符合紧凑规范（默认 th/td padding 6px 10px、line-height 1.2；表格内 Tag 紧凑化）

## 审查要点
- Tauri：`#[tauri::command]` + `#[specta::specta]` 是否齐全
- 类型：入参/出参 `specta::Type` 与 camelCase 一致
- 数据库：`sqlx::query_as!`、显式列名、事务正确
- 前端：仅用 `commands`，错误 `message.*` 提示
- 性能：重复计算、N+1、无谓 clone

## 快速命令
```bash
cargo clippy --all-targets --all-features -- -D warnings
cargo fmt --all
cd frontend && npm run lint
```

## 反馈结构
- 先列出问题（严重性排序）
- 给出可操作修复建议
- 标注文件路径与关键位置

## 检查清单
- [ ] 关键路径无回归风险
- [ ] Tauri 命令与类型导出完整
- [ ] 前端无 `console.*` / `as any`
- [ ] Lint/Clippy 无警告
- [ ] 表格行高与内边距保持紧凑统一

Overview

This skill performs focused code reviews for a WeChat chat auto-reply assistant, emphasizing Rust/Tauri backends, React frontends, database usage, and performance risks. It surfaces logic errors, regression risks, and interface mismatches, then produces prioritized, actionable feedback with file locations. Reviews aim to reduce runtime bugs, unsafe patterns, and UI inconsistencies quickly.

How this skill works

The skill scans code for critical patterns: Tauri command annotations, Specta type export consistency, explicit SQL column usage, and common frontend anti-patterns like console.* or casting to any. It runs checklist validations (lint/clippy, formatting) and inspects performance issues such as N+1 queries, unnecessary cloning, and repeated computations. Output lists issues sorted by severity and includes concrete fixes and exact file/line hints.

When to use it

Before merging changes that touch Tauri commands or backend RPC surfaces
When adding or modifying API types shared between Rust and the frontend
Prior to database schema or query changes that affect transactions or performance
When frontend UI tables or compact layout rules may be violated
During PR review to catch regressions, lint warnings, or unsafe casts

Best practices

Prioritize logical regressions and type mismatches over stylistic nitpicks
Ensure #[tauri::command] and #[specta::specta] are present for exposed functions
Use explicit column lists with sqlx::query_as! and validate transactions
Avoid console.* and as any in frontend code; prefer typed command responses
Run cargo clippy --all-targets --all-features -D warnings and frontend linters before review

Example use cases

Detect a missing specta export on a new Tauri command that breaks type generation
Identify an N+1 database query introduced in a message history endpoint
Find frontend table padding or line-height deviations that break compact layout
Spot an unsafe any cast in React that could hide a runtime error
Recommend converting repeated expensive computations into memoized results

FAQ

What severity levels are used?

Issues are grouped by severity: Blocker (regressions, security/transaction errors), High (type mismatches, performance hotspots), Medium (lint warnings, minor UI rules), Low (stylistic suggestions).

How are fixes presented?

Each finding includes a short description, reproducible steps or code snippets for a fix, and a file path with the key lines to change.