code-review
Review code for common issues and project conventions. Use when reviewing PRs, checking code quality, or before committing changes.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install legacy3-wowlab-code-review
Repository
Skill path: .claude/skills/code-review
Review code for common issues and project conventions. Use when reviewing PRs, checking code quality, or before committing changes.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: legacy3.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install code-review into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/legacy3/wowlab before adding code-review to shared team environments
- Use code-review for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: code-review description: Review code for common issues and project conventions. Use when reviewing PRs, checking code quality, or before committing changes. allowed-tools: Read, Grep, Glob --- # Code Review Read-only review skill for checking code quality against project conventions. ## Checklist ### Portal Components - [ ] Pages are minimal (just render component) - [ ] `loading.tsx` uses `*Skeleton` component - [ ] `"use client"` only where needed - [ ] Barrel exports in `index.ts` - [ ] Data hooks live in `lib/refine/services/` (not in hooks/) - [ ] Loading states use Loader components from `@/components/ui/loader` (not Loader2 from lucide) - [ ] Styling uses Panda CSS (`css()`, `styled()`, layout components from `styled-system/jsx`) ### General - [ ] No unused imports or variables - [ ] No `console.log` in production code - [ ] Error handling is comprehensive - [ ] Types are explicit at module boundaries - [ ] Control flow has braces (no single-line if/for) - [ ] No backwards-compat shims or deprecated code - [ ] No type casts (`as Type`) — use `satisfies` instead ## How to Use 1. I'll read the files you want reviewed 2. Check against the patterns above 3. Report issues with file:line references 4. Suggest fixes where applicable