Investigate code to confirm specifications and provide evidence-based reports. Use for questions like 'what does this do?', 'how is this implemented?', 'where is the spec?', 'explain this behavior', or any request requiring code investigation with documented evidence. Also use for bug investigation requiring current specification understanding.
Reverse-engineers specifications from existing code. Use when user says "document what this code does", "create specs from existing code", "I need to understand this codebase before changing it", "audit the code", "what does this feature actually do", "retrofit specs", or mentions brownfield, legacy code, or undocumented systems.
Analyzes a codebase to generate comprehensive architectural documentation including technologies used, data flows, functional components, APIs, external dependencies, commit history analysis, and complexity hotspots.
Deep codebase analysis to generate 8 comprehensive documentation files. Adapts based on path choice - Greenfield extracts business logic only (tech-agnostic), Brownfield extracts business logic + technical implementation (tech-prescriptive). This is Step 2 of 6 in the reverse engineering process.
Testing guidelines for Bun/TypeScript projects using bun:test framework. Use when writing tests, creating test files, debugging test failures, setting up mocks, or reviewing test code. Triggers on *.test.ts files, test-related questions, mocking patterns, and coverage discussions.
Analyze GDScript code for quality, best practices, anti-patterns, and refactoring opportunities. Use this when the user wants to review code quality, check for Godot-specific issues, or improve code maintainability.
Comprehensive test coverage analysis and improvement for Ruby and Rails applications using SimpleCov and SimpleCov Console formatter. Automatically runs coverage reports, identifies gaps, suggests tests, and enforces coverage standards. Integrates with RubyCritic for holistic code quality. Use when running tests, analyzing coverage, improving test suites, or setting up coverage tracking in Ruby/Rails projects.
Review code for best practices, bugs, and security issues. Use when the user asks to review code, check for problems, or analyze code quality.
Optimizes browser usage to reduce system overhead and ensures code quality via console verification.
Performs thorough code reviews with actionable feedback. Analyzes code for quality, bugs, security vulnerabilities, performance issues, and best practices violations. Use when the user wants a code review or asks to check code for issues.
Perform comprehensive dead code and clean-up analysis in Python projects using static analysis, coverage, dependency checks, and security scanning. Use when asked to clean up code, find unused code, analyze dependencies, or improve code quality.
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.
コード品質の専門家。品質・セキュリティ・パフォーマンスの観点からコードをレビュー。使用場面: (1) コードレビュー、(2) バグ発見、(3) パフォーマンス改善提案、(4) セキュリティ脆弱性チェック、(5) ベストプラクティス適用確認。トリガー: "code-reviewer", "コードレビュー", "レビュー", "品質確認", "/code-reviewer"
Expertise in reviewing code for style, security, and performance. Use when the user asks for "feedback," a "review," or to "check" their changes.
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.
Review test coverage and quality. Analyzes unit tests, integration tests, determinism, and test design. Use when reviewing test files or code that should have tests.
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
This skill should be used when reviewing test code, the user asks "is this test good", "test quality", "mock properly", or when tests behave unexpectedly. Identifies common testing mistakes.
Comprehensive code review focusing on quality, security, performance, and best practices. Use when reviewing PRs, commits, or code changes.
Scans code for security vulnerabilities and unsafe patterns. Use when the user asks about security, mentions OWASP, credentials, secrets, XSS, SQL injection, or wants to audit code for threats.
Analyzes code complexity metrics and identifies areas that are too complex for developers to easily understand
