cc-workflows:review-code
Performs thorough code reviews covering code quality, security, architecture, and UI/UX. Use when reviewing code changes, PRs, implementations, or when asked to review, audit, or assess code quality. Generates detailed reports with prioritized findings.
What this skill does
# Code Review Skill Comprehensive code review covering quality, security, architecture, and UI/UX aspects. ## Instructions - **Fully** read and understand the **Workflow Rules, Guardrails and Guidelines** section in CLAUDE.md (and/or system prompt) before starting work, including but not limited to: - **Foundational Rules and Guardrails** - **Foundational Development Guidelines and Standards** (e.g. Development, Architecture, UI/UX Guidelines etc.) - **Non-modifying** - Analysis only, no code changes - Follow project guidelines from CLAUDE.md - Use checklists in `checklists/` subdirectory for systematic assessment ## Workflow ### Phase 1: Context Analysis 1. **Determine review scope** from conversation context: - If specific files/dirs mentioned: Focus on those - If PR number mentioned: Run `gh pr diff <number>` to get changes - If focus area mentioned (security, architecture, ui): Emphasize in Phase 2 - Otherwise: Use git status/diff for scope 2. Run `git status --porcelain` and `git diff` to identify changes 3. Run `git log -10 --oneline` to understand recent commits 4. Use `tree -d -L 3` and `git ls-files | head -250` for codebase overview 5. Identify applicable review types based on changed files (code, architecture, UI/UX) 6. Read additional relevant guidelines and documentation (API, guides, reference, etc.) as needed 7. **Verify against authoritative sources** - When reviewing technical choices, API usage, security patterns, or framework conventions, look up official documentation to verify findings are based on current facts (not outdated assumptions). Use web searches and Context7 MCP as needed. **Gate**: Scope determined, relevant files identified ### Phase 2: Review Execution Perform applicable reviews using the checklists. #### Code Analysis - Run static analysis, linting, type checking per project guidelines - Use IDE diagnostics if available - **IMPORTANT**: Only format code that has been added or modified, **NEVER** format the entire codebase #### Code Review **Checklist**: [CODE-REVIEW-CHECKLIST.md](checklists/CODE-REVIEW-CHECKLIST.md) Assess: - Correctness, logic errors, edge cases, error handling - Readability, naming, code organization - Best practices, DRY, design patterns, anti-patterns - Performance (N+1 queries, algorithms, caching) - Maintainability, testability, documentation, tech debt #### Security Review **Checklist**: [SECURITY-REVIEW-CHECKLIST.md](checklists/SECURITY-REVIEW-CHECKLIST.md) Assess: - Input validation & sanitization - Injection prevention (SQL, command, XSS, path traversal) - Authentication & authorization - Cryptography (encryption, hashing, key management) - Data protection (secrets, logging exposure) - API security, headers, CORS, CSRF - OWASP Top 10 coverage #### Architecture Review **Checklist**: [ARCHITECTURAL-REVIEW-CHECKLIST.md](checklists/ARCHITECTURAL-REVIEW-CHECKLIST.md) Assess: - CUPID principles (Composable, Unix philosophy, Predictable, Idiomatic, Domain-aligned) - DDD patterns (bounded contexts, aggregates, domain events) - Pattern adherence (clean architecture, service boundaries, API design) - Anti-patterns, performance, scalability, resilience #### UI/UX Review (when applicable) **Checklist**: [UI-UX-REVIEW-CHECKLIST.md](checklists/UI-UX-REVIEW-CHECKLIST.md) Assess: - Visual quality (layout, typography, color/contrast, responsive) - Usability (5-second clarity, touch targets, cognitive load) - Platform conventions (iOS HIG, Material Design, web standards) - Accessibility (WCAG 2.2), performance, interaction patterns **Gate**: All applicable reviews complete ### Phase 3: Analysis & Findings 1. Categorize findings by priority: - **CRITICAL**: Security vulnerabilities, data loss risks, broken functionality - **HIGH**: Performance issues, maintainability concerns, minor security issues - **SUGGESTIONS**: Improvements, optimizations, enhancements 2. Identify obsolete/temporary files and code requiring cleanup 3. Check for unmotivated complexity, over-engineering, or duplication 4. Verify adherence to project guidelines and patterns **Gate**: Findings categorized and validated ## Report Format Generate markdown report with: ```markdown # Review Report - [Date] ## Summary [2-3 sentence overview of review scope and overall assessment] ## CRITICAL ISSUES [Each issue: Title, Impact, Location, Fix Required] ## HIGH PRIORITY [Each issue: Title, Impact, Location, Recommendation] ## SUGGESTIONS [Brief list of improvements] ## Cleanup Required - [Obsolete/temporary files to remove] - [Dead code to remove] ## Compliance - Guidelines adherence: [Assessment] - Architecture patterns: [Assessment] - Security best practices: [Assessment] - [UI/UX if applicable]: [Assessment] ## Next Steps 1. [Prioritized action items] ``` Store report at: `<project_root>/.agent_temp/reviews/<feature-name>-code-review-<YYYY-MM-DD>.md` Return report location to user.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.