A code-review checklist for the CalendarCN project, focused on pull requests, diffs, TypeScript types, React patterns, component structure, imports, and styling. A code review examines proposed changes before they are merged.

Use it when reviewing CalendarCN pull requests or code changes, especially React components and TypeScript files, to check hooks, props, imports, state updates, and Tailwind styling.

It helps catch project-specific consistency, type-safety, React, and styling problems early. It gives reviewers a concrete standard instead of relying only on personal preferences.

How vmnog/calendarcn configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to vmnog/calendarcn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vmnog/calendarcn/main/.claude/skills/code-review/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/vmnog/calendarcn

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vmnog/calendarcn/code-review/github.svg)](https://agentmods.dev/skills/vmnog/calendarcn/code-review)

Your own site

<a href="https://agentmods.dev/skills/vmnog/calendarcn/code-review"><img src="https://agentmods.dev/badge/skills/vmnog/calendarcn/code-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vmnog/calendarcn/code-review"><img src="https://agentmods.dev/badge/skills/vmnog/calendarcn/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 607 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00607
Opus 5.5	$0.00000	$0.00243
Sonnet 5.5	$0.00000	$0.00121
Haiku 4.5	$0.00000	$0.00061

Measured 28d ago against content hash 5e6a4422d3d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 28d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/code-review/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review Skill — CalendarCN

When to Use

Invoke when reviewing PRs, diffs, or code changes in the CalendarCN project.

Checklist

1. Type Safety

No any types introduced
All shared types imported from week-view-types.ts (not duplicated)
import type used for type-only imports
Props defined via interface ComponentNameProps
Optional props use ? (not | undefined)

2. React Patterns

ref.current never assigned during render (always in useEffect)
Hook dependencies are exhaustive (no eslint-disable for deps)
Refs used to break circular dependencies (not skipped deps)
React.useCallback for handlers passed as props
React.useMemo for expensive derived state
No state updates during render

3. Component Structure

"use client" directive present if component uses hooks/browser APIs
Import order: external → @/lib/utils → @/hooks → @/components → @/lib
Constants in ALL_CAPS with JSDoc
Early returns instead of deeply nested conditionals
Props destructured in function params

4. Styling

Uses cn() for conditional classes (no string concatenation)
Tailwind for fixed styles, inline style for computed layout
Color variants use eventColorStyles[color] map
Z-index follows scale: events(0-2) < selected(20) < placeholder(25) < dragging(30) < portal(9999)
Dark mode tested (uses CSS variables, not hardcoded colors)

5. Naming

Files: kebab-case
Components: PascalCase
Hooks: useCamelCase
Constants: ALL_CAPS_SNAKE

6. Performance

No unnecessary re-renders (check memoization)
Event listeners cleaned up in useEffect return
ResizeObserver disconnected on unmount
Large computations memoized (e.g., calculatePositionedEvents)

7. Pre-submit

pnpm lint && pnpm typecheck && pnpm format:check

All three must pass before approving.

Read the full file on GitHub · 72 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

28d ago First seen · 72 lines · 0 tokens per session scan A 5e6a4422d3d6

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository vmnog/calendarcn (139 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 607 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.

Code review calendar nextjs shadcn-ui tailwindcss

tuturuuu-review-comments

Inspect, fix, and resolve Tuturuuu pull-request review threads.

tutur3u/platform · 20 tokens

ui-beats

Use this skill when users want to add, customize, or troubleshoot UI Beats components in React/Next.js projects. It covers component selection, shadcn registry installation from uibeats.com, the UI Beats MCP server, motion and reduced-motion handling, and integration patterns for animated sections.

nikhils4/ui-beats · 62 tokens

react-doctor

Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.

shipkit-io/bones · 31 tokens

code-review

Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.

williamjxj/friendshipdaycare · 26 tokens

migrate-radix-to-base

Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.

shadcn-ui/ui · 61 tokens

magic-ui

Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.

magicuidesign/magicui · 56 tokens

calendarcn: Skill for Claude Code