本文へ移動
cccskills
無料GitHub で公開

code-review

Review code for quality, security, performance, and maintainability. Use when reviewing PRs, auditing a codebase, or refactoring. Covers TypeScript, Node.js, infrastructure-as-code, and full-stack web apps.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Code Review

Systematic code review for Espen's TypeScript/Node.js projects.

Process

  1. Understand scope — Read the changed files or the area under review:

    # For git changes
    git diff --name-only HEAD~1
    git diff HEAD~1
    
    # For a specific area
    find src/ -name "*.ts" -newer <reference-file>
    
  2. Read the code — Use the read tool on each file. Don't guess.

  3. Analyze against checklist — Score each category.

  4. Report — Use the output format below.

Review Checklist

Correctness

  • Logic handles edge cases (null, empty, boundary values)
  • Error handling is explicit (no swallowed errors, no bare catch {})
  • Async code handles rejection/cancellation properly
  • Types are accurate (no unnecessary any, proper narrowing)

Security

  • No secrets or credentials in code
  • User input is validated/sanitized before use
  • SQL queries use parameterized statements (no string interpolation)
  • File paths are resolved safely (no path traversal)
  • Auth checks are present where needed

Performance

  • No N+1 queries or unbounded loops over large datasets
  • Heavy operations are async or streamed (not blocking)
  • Database queries use appropriate indexes
  • Large responses are paginated or truncated

Maintainability

  • Functions do one thing with clear names
  • No magic numbers or hardcoded values that should be config
  • Types and interfaces are defined (not inline object shapes)
  • Dead code and unused imports are removed
  • Comments explain why, not what

Project Conventions

  • Follows existing patterns in the codebase
  • File naming and directory structure is consistent
  • Error messages are helpful for debugging
  • Logging is appropriate (not too noisy, not silent on errors)

Output Format

## Code Review: [scope]

### Summary
One paragraph: what the code does, overall quality assessment.

### Issues

#### 🔴 Critical
- [file:line] Description and fix

#### 🟡 Important
- [file:line] Description and suggestion

#### 🔵 Minor
- [file:line] Nit or style suggestion

### What's Good
- Call out well-written code, good patterns, clever solutions

### Recommendations
- Prioritized list of changes, starting with most impactful

Common Patterns in Espen's Stack

Project TypeKey Things to Check
Pi extensionsTool parameter schemas, error returns, signal/abort handling
Eleventy sitesTemplate data flow, permalink structure, Tailwind purge config
TanStack appsRouter setup, query keys, optimistic updates, Clerk auth guards
InfrastructureTerraform state safety, Docker layer caching, env var handling
SQLiteMigration ordering, prepared statements, WAL mode, index coverage

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Audit, generate, update, and lint AGENTS.md files across all projects. Use when asked to check project context files, scaffold AGENTS.md for new projects, update stale ones, or run a cross-project audit.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年9月22日 更新

blog-post

無料

Draft, edit, and publish blog posts for e9n.dev. Use when creating new posts, editing drafts, or refining existing content. Handles Eleventy frontmatter, Tailwind formatting, and Espen's authentic voice.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年9月22日 更新

Generate a full operational status report for the Aivena bot. Checks all subsystems: extensions, webserver, Telegram, chat bridge, heartbeat, cron, database, memory, CRM, calendar, task management, jobs/telemetry, and storage. **Triggers — use this skill when:** - User asks for "status", "bot status", "system status", "operational status" - User asks "is everything running?", "how's Aivena doing?" - User says "health check", "diagnostics", "systems check" - User asks "what's the state of the bot?"

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年9月22日 更新

Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年9月22日 更新

cmux

無料

Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年9月22日 更新

Generate and maintain AI-readable markdown documentation for a codebase in docs/. Use this skill whenever the user asks to document their codebase, generate project docs, create architecture docs, update documentation after code changes, build a knowledge base for AI agents, create onboarding docs, map out a codebase, or explain a project structure. Also trigger when users say things like "document this repo", "create docs for my project", "update the docs", "write architecture documentation", "help AI understand my code", "generate a codebase overview", or "maintain docs". This skill is specifically about creating structured markdown files in a docs/ directory that serve as a knowledge base — NOT about writing inline code comments, README files, or API reference docs from docstrings.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年9月22日 更新

espennilsen のスキルをすべて見る

このスキルの問題を報告する