code-review
Perform structured code reviews focusing on correctness, readability, security, and maintainability. Use this skill when reviewing pull requests, evaluating code changes, or establishing review standards for a team.
What this skill does
# Code Review Perform structured, actionable code reviews. ## When to Use - Reviewing a pull request or set of changes - Evaluating code quality before merging - Auditing a module for technical debt - Establishing review standards or checklists ## Review Dimensions Review code across these dimensions, in priority order: ### 1. Correctness - Does the code do what it claims? - Are edge cases handled? (null, empty, overflow, concurrency) - Are error paths tested? - Do tests cover the changed behavior? ### 2. Security - Input validation at system boundaries - No secrets in code (API keys, passwords, tokens) - SQL/command injection prevention - Proper authentication and authorization checks - See `security-audit` skill for deeper analysis ### 3. Readability - Clear naming (variables, functions, classes) - Functions do one thing - No deep nesting (max 3 levels) - Comments explain "why", not "what" - Consistent style with the surrounding codebase ### 4. Maintainability - No unnecessary abstractions - DRY without over-abstraction (rule of three) - Dependencies are justified - Breaking changes are flagged ### 5. Performance - Only flag when there is a real concern (hot path, large data, N+1 queries) - Do not micro-optimize unless the context demands it ## Review Output Format Structure feedback as: ```markdown ## Review: <PR title or file> ### Must Fix - [ ] **file.py:42** — [Correctness] Description of the issue and suggested fix ### Should Fix - [ ] **file.py:78** — [Readability] Description and suggestion ### Consider - [ ] **file.py:100** — [Performance] Optional improvement ### Positive - file.py:15 — Good use of context manager for resource cleanup ``` **Severity levels:** | Level | Meaning | Merge? | |-------|---------|--------| | Must Fix | Bug, security issue, or broken contract | Block | | Should Fix | Significant readability/maintainability concern | Request changes | | Consider | Optional improvement, style preference | Approve with comment | | Positive | Good patterns worth highlighting | - | ## Guidelines 1. **Be specific** - Point to exact lines, suggest concrete alternatives 2. **Explain why** - "This could cause X because Y", not just "change this" 3. **Separate style from substance** - Automate style (linters); review logic manually 4. **Limit scope** - Review what changed, not the entire file (unless asked) 5. **Acknowledge good work** - Include at least one positive observation 6. **Propose, don't impose** - "Consider using X" not "You must use X" (unless it's a Must Fix)
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.