code-review
Reviews code for bugs, security issues, performance problems, and adherence to best practices. Use when the user asks to "review this code", "check my code", "is this code good?", or before submitting a PR.
What this skill does
# Code Review Skill When reviewing code, follow this structured process: ## 1. Understand the Context - What does this code do? Summarize its purpose in 1-2 sentences - What files were changed and why? - If reviewing a diff, understand both the before and after ## 2. Correctness - Are there any logic bugs? - Are edge cases handled (null, empty, zero, negative, boundary values)? - Are error paths handled properly with meaningful error messages? - Are return types and values correct? - Are async operations handled properly (missing await, race conditions)? ## 3. Security - SQL injection or NoSQL injection risks - XSS vulnerabilities (unsanitized user input rendered in HTML) - Hardcoded secrets, API keys, or credentials - Insecure use of eval(), innerHTML, or dynamic code execution - Missing authentication or authorization checks - Sensitive data exposure in logs or error messages ## 4. Performance - Unnecessary loops or O(n²) operations - Missing database indexes for frequent queries - N+1 query problems - Large objects held in memory unnecessarily - Missing pagination on list endpoints - Expensive operations inside loops that could be batched ## 5. Readability & Maintainability - Are variable and function names clear and descriptive? - Are functions small and focused (single responsibility)? - Is there duplicated code that should be extracted? - Are magic numbers or strings replaced with named constants? - Is complex logic commented or self-documenting? ## 6. Testing - Are there tests for the new/changed code? - Do tests cover happy path AND error cases? - Are tests testing behavior, not implementation details? - Are mocks used appropriately (not over-mocked)? ## 7. Project Standards - Does the code follow the project's existing patterns and conventions? - Are imports organized consistently? - Does it match the linting and formatting rules? - Are types properly defined (no unnecessary `any` in TypeScript)? ## Output Format For each issue found, report it as: **[SEVERITY] Category — File:Line** Description of the issue. Suggested fix: ``` // corrected code here ``` Severity levels: - 🔴 **CRITICAL** — Bugs, security vulnerabilities, data loss risks. Must fix. - 🟡 **WARNING** — Performance issues, missing error handling, potential problems. Should fix. - 🟢 **SUGGESTION** — Readability, style, minor improvements. Nice to have. ## Summary End every review with: 1. **Overall assessment** — Is this safe to merge? (Yes / Yes with changes / No) 2. **Critical issues count** — How many must-fix items 3. **Top 3 things done well** — Always highlight positives 4. **Top 3 improvements** — Most impactful changes to make
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.