Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C#, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A relentless interview to sharpen a plan or design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design". Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.