code-review
Review code for quality, security, and correctness with severity-based feedback
Review code for quality, security, and correctness with severity-based feedback
Follow core coding style principles including SOLID, DRY, KISS, and YAGNI when writing code. Apply consistent naming conventions, meaningful variable names, small focused functions, automated formatting, and proper code organization. Use this skill across all programming languages and file types when writing or refactoring code. Use when creating functions, classes, modules, or components to ensure Single Responsibility Principle, when avoiding code duplication (DRY), when choosing simple over clever implementations (KISS), or when resisting premature optimization and speculative features (YAGNI). Use when establishing naming conventions, removing dead code, or maintaining consistent indentation and formatting. Apply these principles universally across backend (.ts, .js, .py, .java, .go), frontend (.tsx, .jsx, .vue), and configuration files.
코드 변경 사항에서 버그, 스타일 이슈 및 베스트 프랙티스를 검토합니다. PR 리뷰나 코드 품질 확인 시 사용하세요.
Best practices for writing high quality production grade Python code
Automatically monitor, evaluate, and resolve CodeRabbit and Qodo PR review comments. Waits for review bots to comment, evaluates suggestions intelligently, applies fixes, and marks comments as resolved. Designed to run in ralph-loop for continuous operation. Triggers: "resolve PR comments", "fix review issues", "handle coderabbit", "address qodo feedback", "PR review loop", "/pr-resolve"
Validate file placement against canonical structure rules and auto-fix violations. Use before committing or when validating project structure.
Python code style and type hinting patterns. Use when writing or reviewing Python code to ensure consistent, modern type annotations, clean code structure, and proper separation of concerns. Covers modern type hints, import organization, router-service separation, comment practices, and docstring conventions.
Review and lightly edit a single blog post under _posts/ for prose quality and source hygiene, without changing code examples or post structure.
Sets up Node.js/TypeScript development environment with npm/yarn, dependencies, ESLint, Prettier, testing (Jest/Vitest), and TypeScript type checking. Ensures consistent tooling configuration. Use when starting work on Node.js/TypeScript projects, after cloning repositories, setting up CI/CD, or troubleshooting environment issues.
Validate JSON file formats by scanning directories and checking for correct JSON syntax
Audit and fix accessibility issues for WCAG 2.1 AA compliance. Use when reviewing UI components, implementing forms, building modals, or before releases.
Use when doing a quick preflight to assess scope, risks, and priorities for Python research code refactoring.
Enforces visibility pattern for testability by detecting private methods that prevent unit testing (causes 20-40% coverage loss). References authoritative style guides rather than duplicating. Auto-refactors code to private[module] object pattern with user approval. Detects inline lambdas and suggests extraction to named functions ("laws"). Blocks during scala-ninja review (Phase 2) as peer review rejection point.
Distill a failure into a reusable principle and preflight check.
Conduct thorough, actionable code reviews that catch real problems without drowning in noise
Use this agent when you need to analyze code quality
License checking and compatibility. Use when evaluating dependency licenses.