code-review

Estrellas9

Forks0

Actualizado14 de abril de 2026 a las 08:17

Review changed code for Lumen project conventions — catches gotchas that linters miss like wrong hash function, FTS5 quoting, missing .js extensions, interface instead of type. TRIGGER when user asks to review, check, or audit code they wrote.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

Sardor-M

Sardor-M/lumen

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

Explorador de archivos

2 archivos

SKILL.md

readonly

name	code-review
description	Review changed code for Lumen project conventions — catches gotchas that linters miss like wrong hash function, FTS5 quoting, missing .js extensions, interface instead of type. TRIGGER when user asks to review, check, or audit code they wrote.

Lumen Code Review

Review changed files against the project rules in CLAUDE.md and the codebase-specific pitfalls in references/gotchas.md.

Steps

Run pnpm lint and npx prettier --check "src/**/*.ts" to catch automated issues
Read each changed file and check against CLAUDE.md rules and references/gotchas.md
Report findings grouped by severity: must fix, should fix, nit

Focus on things linters cannot catch: wrong hash function for dedup, unquoted FTS5 terms, missing transaction for batch inserts, Commander async without try/catch, singleton state leaks in tests.

Output

[must fix|should fix|nit] file:line — description

Fix must fix and should fix automatically. Ask before fixing nits.

If more than 5 files, spawn a subagent for the review and implement fixes based on its findings.

Más de este repositorio

mismo repositorio

debug-lumen

Sardor-M/lumen

Diagnose Lumen CLI or MCP issues — common errors, SQLite problems, search returning no results, compilation failures. TRIGGER when user reports a bug, error, or unexpected behavior.

2026-04-239

deploy-check

Sardor-M/lumen

Pre-deploy verification for Lumen monorepo — type check, lint, test, build across all workspaces. TRIGGER when user says deploy, ship, release, pre-merge, or CI check.

2026-04-239

monorepo-guide

Sardor-M/lumen

Reference for navigating the Lumen turborepo — workspace commands, where things live, cross-app imports. TRIGGER when user asks about project structure, where to put files, or how workspaces connect.

2026-04-239

lumen-mcp

Sardor-M/lumen

Search, query, and explore the Lumen knowledge base via MCP tools. TRIGGER when user invokes /lumen or asks about their knowledge base, sources, concepts, or graph.

2026-04-139

web-page

Sardor-M/lumen

Scaffold a new page or component for the Lumen Next.js web app. TRIGGER when user asks to create, add, or build a new page, route, or dashboard section.

2026-04-139

new-command

Sardor-M/lumen

Scaffold a new Lumen CLI command following the Commander.js register pattern. TRIGGER when user asks to create, add, or implement a new CLI command or subcommand.

2026-04-079

name	code-review
description	Review changed code for Lumen project conventions — catches gotchas that linters miss like wrong hash function, FTS5 quoting, missing .js extensions, interface instead of type. TRIGGER when user asks to review, check, or audit code they wrote.

Lumen Code Review

Review changed files against the project rules in CLAUDE.md and the codebase-specific pitfalls in references/gotchas.md.

Steps

Run pnpm lint and npx prettier --check "src/**/*.ts" to catch automated issues
Read each changed file and check against CLAUDE.md rules and references/gotchas.md
Report findings grouped by severity: must fix, should fix, nit

Focus on things linters cannot catch: wrong hash function for dedup, unquoted FTS5 terms, missing transaction for batch inserts, Commander async without try/catch, singleton state leaks in tests.

Output

[must fix|should fix|nit] file:line — description

Fix must fix and should fix automatically. Ask before fixing nits.

If more than 5 files, spawn a subagent for the review and implement fixes based on its findings.