review
Review specification and developer documents for compliance with project guidelines. Use when checking docs-spec/ and docs-site/docs/ for ambiguous expressions or missing required sections.
Discover tools code quality skills, compare source repositories and read the instructions for each workflow.
Review specification and developer documents for compliance with project guidelines. Use when checking docs-spec/ and docs-site/docs/ for ambiguous expressions or missing required sections.
Check and synchronize specification documents (docs-spec/) with implementation (src/, src-tauri/, tests/). Detect discrepancies and auto-fix when possible.
Find dead code, duplications, complexity issues, and refactoring opportunities. Use when cleaning up code, removing unused exports, simplifying complex functions, or during tech debt sprints.
Find bugs, logic errors, race conditions, and edge cases in code. Use when investigating issues, reviewing complex logic, checking async code, or looking for potential runtime errors.
Use this agent when you need to analyze code quality
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
This skill should be used when reviewing code or running /uw:review. It contains 47 issue patterns with severity tiers, team standards to enforce, and implementation checklists for the Unit Work review system.
Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.
Validate plan document structure and frontmatter. Use when checking plans for compliance, ensuring proper formatting, or verifying metadata before commits.
Validate CLAUDE.md structure, formatting, and quality. Use when checking context files for compliance, ensuring proper structure, or verifying before commits.
Review user doc quality. Use when checking documentation completeness, accuracy, readability, and ensuring examples work correctly.
Automatically selects appropriate review perspectives based on file type and characteristics. Use when initiating code review to determine which review-points files should be applied.
Defines project-wide code conventions for magic number elimination, constant usage, performance optimization, and type safety. Use when implementing, testing, or reviewing code to ensure consistency across the...
Code formatting with Prettier for TypeScript/NestJS projects. Trigger: After editing/creating files, before committing code, ensuring code style consistency.
Use when creating or editing markdown files to ensure strict compliance with markdownlint rules and professional markdown best practices
Skill para mantener la calidad del código: linting, formatting, type checking. Garantiza que el código cumple con los estándares del proyecto.
Guía para refactorizar código Python de forma segura y efectiva. Incluye técnicas de refactoring, detección de code smells, y mejoras.
Testing best practices for modern Python development. Activated when working with tests, pytest, Hypothesis property-based testing, Atheris fuzz testing, test coverage, test organization, or mutation testing.
Type safety best practices for modern Python development. Activated when working with type hints, basedpyright, typing-extensions, Protocol, TypedDict, generics, or type narrowing.
Python development best practices for modern Python projects. Activated when working with Python files, pyproject.toml, or discussing Python patterns, testing, linting, type hints.
Use when performing code reviews. Provides a checklist to verify error handling, TypeScript, CSS, and architecture patterns.
Use when generating or modifying code to ensure it follows project architecture and development guidelines. Enforces Result-based error handling, TypeScript conventions, and frontend architecture patterns.
모든 코드 변경 시 반드시 사용. 어떤 변경이든 관련 문서가 있는지 점검하고 최신화 필수. docs/, CLAUDE.md, Swagger 애노테이션이 코드와 일치하는지 확인.
모든 코드 변경에 항상 적용되는 프로젝트 규칙. 프로젝트 구조, API 규칙, 컨벤션 준수 필수.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.