Essential command-line tools and system utilities.
Code quality checker skill. This skill should be used when the user wants to: (1) Run static analysis tools (mypy, pyright, ruff) on the codebase - triggered by "/check", "/check q", or "/check quality" (2) Find dead/unused code (functions, imports, variables, unreachable code) - triggered by "/check d" or "/check dead"
Mandatory verification protocol after code changes for JavaScript/TypeScript projects. Use after any code modification to ensure quality.
Analyze codebase statistics with tokei (line counts by language) and difft (semantic AST-aware diffs). Use for project composition, refactoring scope, codebase metrics.
Analyzes code smells and architectural violations to formulate a concrete Refactoring Plan. Used for (1) identifying technical debt, (2) defining As-Is vs To-Be states, and (3) planning safe, atomic refactoring steps.
Review code written by Claude Code or humans across multiple languages. Use when asked to review, audit, critique, or analyze code quality. Supports R, Python, JavaScript, SQL, C++, Rust, Go, Ansible, Kustomize/Kubernetes, Dockerfiles, Docker Compose, and Bash. Covers correctness, security, performance, testing, documentation, and architecture. Produces actionable output for Claude Code to fix issues plus human-readable REVIEW.md summaries.
ALWAYS use this skill proactively for Consumer Affairs Django repositories (located in ../ca/ directory) when ANY of these occur - (1) After writing or modifying ANY Python code files in CA repos (2) After tests pass and before telling user work is complete (3) User mentions linting, formatting, ruff, code style, or code quality (4) After using the ca-django-tests skill successfully (5) Before preparing to commit code. This skill runs 'ca exec ruff format' and 'ca exec ruff check --fix' to ensure code quality. CRITICAL - Always run this automatically after code changes and before declaring work complete.
Review code for quality, bugs, and best practices. Use when the user says "review this code", "check my implementation", "code quality", "is this code ready", or asks for feedback on specific code. For comprehensive automated reviews that populate REVIEW.md, use the code-auditor agent instead.
Rust coding style guide. Apply automatically when writing or modifying Rust code. Enforces let-else for early returns, variable shadowing, newtypes, explicit matching, and minimal comments.
Spawns 4 parallel review agents (Accessibility, React Router, React Core, Anders Hejlsberg) to conduct comprehensive multi-perspective code reviews
コード品質の専門家。品質・セキュリティ・パフォーマンスの観点からコードをレビュー。使用場面: (1) コードレビュー、(2) バグ発見、(3) パフォーマンス改善提案、(4) セキュリティ脆弱性チェック、(5) ベストプラクティス適用確認。トリガー: "code-reviewer", "コードレビュー", "レビュー", "品質確認", "/code-reviewer"
Review Vendure plugins for best practices violations. Detects missing decorators, improper DI, hardcoded config, lifecycle hook issues, and service anti-patterns. Use when reviewing plugin PRs or auditing plugin quality.
TypeScript conventions for ecommerce monorepo. Covers Next.js, Fastify, Prisma, Zod validation, React Query, and testing patterns. Triggers on "typescript", "type error", "ts", "tsx", "type hints", "zod schema", "prisma", "react query", "next.js", "fastify routes", "api types". PROACTIVE: MUST invoke when writing or editing .ts or .tsx files.
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.
Use after completing file changes - strongest for source code (AST-aware linting, security, tests), lighter support for markdown/config. Dispatches CodeRabbit reviewer subagent. ALWAYS request review before considering work complete.
Apply code quality tools (Ruff, ty, pre-commit) to Python projects. Use PROACTIVELY when code quality issues are detected. Keywords: lint, format, quality, 品質, ruff, type
Automatically applies when reviewing code. Ensures structured review checklist covering correctness, security, performance, maintainability, testing, and documentation.
Expertise in reviewing code for style, security, and performance. Use when the user asks for "feedback," a "review," or to "check" their changes.
Use when reviewing code or before commits - runs 25-point quality checklist (structure, errors, security, performance, testing), identifies code smells, suggests refactorings with examples. Activates when user says "review this", "check my code", mentions "refactor", "optimize", "code quality", or before git commits.
Deep audit of the NET-NiNJA repository to map architecture, entrypoints, dead code, missing wiring, broken imports, duplicated logic, TODOs, placeholder handlers, and GUI elements without backend actions. Use when asked to review the repo structure or produce an audit report, punch list with file/line refs, dependency graph, or known entrypoints list.
Use when creating PRs to enforce code quality standards. Automated detection of anti-patterns, security issues, and code smells. Python 3.8+
Use when performing code reviews. Provides a checklist to verify error handling, TypeScript, CSS, and architecture patterns.
Pattern discovery and code reuse for Python projects. Use when writing new code, implementing features, or refactoring. Triggers on "pattern", "reuse", "duplicate", "extract", "helper", "refactor", "architecture", "existing code", "search for", "similar", "copy", "paste", or when about to write new functionality.
Code review and audit agent for pull requests and code quality
