code-review

Agent Skills › langwatch/langwatch › code-review

code-review

GitHub

基于LangWatch代码规范对项目级代码变更进行自动化审查，涵盖ID生成、多租户隔离、Prisma查询、ClickHouse过滤、类型安全及分层架构等规则。

.claude/skills/code-review/SKILL.md langwatch/langwatch

Trigger Scenarios

需要检查代码变更是否符合项目特定规范时在PR或分支合并前执行代码质量门禁

Install

npx skills add langwatch/langwatch --skill code-review -g -y

More Options

Non-standard path

npx skills add https://github.com/langwatch/langwatch/tree/main/.claude/skills/code-review -g -y

Use without installing

npx skills use langwatch/langwatch@code-review

指定 Agent (Claude Code)

npx skills add langwatch/langwatch --skill code-review -a claude-code -g -y

安装 repo 全部 skill

npx skills add langwatch/langwatch --all -g -y

预览 repo 内 skill

npx skills add langwatch/langwatch --list

SKILL.md

Frontmatter

{
    "name": "code-review",
    "description": "Project-level code review: check changed files against LangWatch codebase rules (IDs, multitenancy, layering, naming, SRP).",
    "argument-hint": "[diff, branch, or commit range]",
    "user-invocable": true
}

Review code changes and sign off on each rule below.

What to diff: If $ARGUMENTS is provided, use it as the diff target (a branch, commit range, or raw diff). Otherwise diff against origin/main, or the PR base branch if on a PR branch. If ambiguous, ask.

For each rule: PASS if no violations, or FAIL with every violation listed — one per line with file:line.

Rules

KSUID only — no uuid/nanoid. The project uses @langwatch/ksuid. No imports of uuid, nanoid, or crypto.randomUUID.
No foreign keys in Prisma migrations. Prisma relations handle referential integrity. No REFERENCES, FOREIGN KEY, or ADD CONSTRAINT.*FOREIGN in .sql migration files.
Prisma queries include projectId. Every findMany/findFirst/findUnique/update/delete on project-scoped models must have projectId in the where clause. Skip: User, Organization, OrganizationUser, Session, Account, VerificationToken.
ClickHouse queries include TenantId. Every ClickHouse query must filter by TenantId in the WHERE clause.
No TypeScript any. No : any, as any, <any>, or any[] in added code. Ignore comments and eslint-disable lines.
No hardcoded schema names in migrations. No "langwatch_db". or other schema prefixes in .sql files. Use unqualified table names.
Hooks don't return JSX. Files matching use*.ts (not .tsx) must not return JSX. Hooks return state/callbacks only.
No re-exports for backwards compatibility. export { X } from or export * from shims are not allowed — update consumers directly. (New public API re-exports are fine.)
Layer violations (route → service → repository). Routes must not import from repositories. Services must not import another domain's repositories directly. Repositories must not import from services. See src/server/app-layer/.
Repository/service method naming. Repositories use findAll/findById (not list*/get*). Services use getAll/getById (not find*).
Single Responsibility. New files should not mix concerns (e.g. HTTP + business logic, data fetching + rendering). One primary export per file. Flag functions over ~100 lines.
Skills must have scenario tests. Any PR that adds or modifies a skill (skills/*/SKILL.md) or MCP tools (mcp/typescript/src/tools/) must include corresponding scenario tests in specs/skills/skills-testing.feature. New tool handlers need at least one @integration scenario covering the happy path.

Output format

### 1. KSUID only (no uuid/nanoid) — PASS

### 2. No FK in migrations — FAIL
- FOREIGN KEY in `migrations/001_init.sql:45`
- ADD CONSTRAINT FOREIGN in `migrations/002_add.sql:12`

### 3. projectId in Prisma queries — FAIL
- `findMany` without projectId in `src/api.ts:33`

### 4. TenantId in ClickHouse queries — PASS

...