'code-review' 검색 결과

Routes quality checks to the appropriate skill, covering code review and fixes, debugging, security checks, acceptance testing, AI response evaluation, and interface reviews. It also directs requests for validating phase outputs or reviewing plans across AI systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code and fix reported issues
• Investigate feature failures and errors
• Check security and acceptance testing

Review code changed during a project phase for bugs, security vulnerabilities, and quality issues. Choose the review depth or specific files, receive findings grouped by severity, and optionally apply fixes followed by another review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing code changed during a phase
• Checking selected source files
• Examining interactions across files

Helps an agent evaluate code review feedback against the actual codebase before making changes. It covers clarifying unclear requests, explaining technical disagreements, prioritizing fixes, and testing each change for regressions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarify ambiguous code review comments
• Check whether suggestions preserve existing behavior
• Explain disagreements using code and test evidence

Review Git code changes using the CodeRabbit CLI. Receive a summary of the changes and issues ordered by severity, with affected file paths, practical impact, and concrete suggestions for follow-up fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing uncommitted code changes
• Checking changes against a base branch
• Organizing quality and security issues by severity

Review Python changes against shared team standards to find bugs, missing regression tests, and security issues. Findings are ordered by severity and include file names and line numbers so reviewers can locate each problem.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing Python changes before merging
• Checking that bug fixes include regression tests
• Finding unsafe SQL and exposed secrets

Review code for readability, security weaknesses, performance bottlenecks, test quality, and ease of maintenance. Receive findings grouped by importance, with explanations and concrete suggestions that reflect the project's context and constraints.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing code quality before merging changes
• Checking security and sensitive data handling
• Finding slow queries and unnecessary API calls

Review code for readability, maintainability, security, and performance. Receive an overview, issues grouped by severity, concrete improvements with code examples, and positive feedback on parts of the implementation that work well.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing an implementation before sharing it
• Checking code for security weaknesses
• Finding performance improvement opportunities

Review code changes for concrete defects. Use it to examine modified code when you want to check whether a change contains a bug, with the review focused on specific problems in the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing changes after editing code
• Checking a bug fix for further defects
• Reviewing code changes that add a feature

Review code changes and pull requests for correctness, security, performance, and test quality. The skill helps prioritize issues, write specific and constructive feedback, and create shared review checklists and standards for a development team.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing code changes and pull requests
• Writing review comments with clear priorities and fixes
• Creating shared review checklists for a team

Review uncommitted changes, commits, branch differences, or pull requests in context. Identify bugs and concrete security weaknesses, explain when each issue occurs and how serious it is, and provide actionable feedback grounded in the surrounding code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing uncommitted changes before a commit
• Checking a specific commit or branch difference
• Reviewing a pull request before merging

Review changes to a multilingual source code parser, focusing on whether relationships between code elements are correct. Check consistency across languages and verify that test examples reproduce the issue and actually validate the fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking constructor call and instantiation relationships
• Reviewing name resolution and scope handling
• Checking whether a parser fix applies to other languages

Check a Kiln branch or pull request through real browser interactions. Multiple agents test separate feature areas in isolated environments, then combine findings into a severity-ranked Markdown report with reproduction steps and expected versus actual behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking all new behavior in a branch or pull request
• Testing multiple feature areas in parallel
• Finding UI text issues and inconsistent interactions

Turn a specification and its linked tickets into code. Multiple agents work on available tasks in separate worktrees, combine changes on one integration branch, and complete a code review before preparing the result for review or closing tickets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a specification and its linked tickets
• Working through tasks with blocking dependencies
• Coordinating parallel implementation in separate worktrees

Build features or fix bugs by writing one failing test, then the minimum code needed to pass it. Test agreed public interfaces, the boundaries callers use, to check behavior without depending on internal implementation details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a feature through test-first development
• Fixing a bug with a failing test first
• Writing behavior-focused integration tests

Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a branch or pull request
• Check changes since a specific commit
• Find missing requirements or unintended scope

Review code changes and pull requests for correctness, security, performance, and test quality. The skill helps prioritize issues, write specific and constructive feedback, and create shared review checklists and standards for a development team.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing code changes and pull requests
• Writing review comments with clear priorities and fixes
• Creating shared review checklists for a team

Review web application code against OWASP Top 10 (2021), a list of common security risks. Receive findings with file locations, severity ratings, concrete fix code, and a prioritized list of remediation tasks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a project's OWASP Top 10 security coverage
• Checking code for SQL injection and XSS
• Inspecting authentication and access controls

Review code with multiple AI perspectives to identify quality, security, performance, and design issues. The workflow also examines test evidence and unfinished implementation, then combines findings into a review that can be shared on a pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request for security issues
• Checking API error handling
• Assessing authentication test coverage

Review code changes for bugs, security risks, design issues, and test quality, then turn findings into specific, prioritized feedback. Use its checklists and comment templates to establish consistent review standards and support developer mentoring.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing pull requests
• Creating team review checklists
• Mentoring junior developers through feedback

Evaluate code review feedback against the actual code, supported environments, and existing behavior. Clarify uncertain requests, respond with technical evidence, and implement valid changes one at a time with tests for each fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying ambiguous code review comments
• Checking whether suggested changes preserve compatibility
• Assessing whether a requested feature is actually used

Analyze complex tasks before implementation through four structured phases. Clarify the problem, examine dependencies and impacts, challenge assumptions, and compare alternatives to produce a decision rationale, explicit uncertainties, and actionable recommendations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying requirements before implementation
• Comparing options and their tradeoffs
• Anticipating failures before work begins

Evaluate existing code review comments against the actual codebase before making changes. The skill guides clarification, technical responses, prioritized fixes, and individual testing, helping assess whether suggestions fit current behavior and compatibility requirements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing CodeRabbit or GitHub review comments
• Clarifying ambiguous requests before making changes
• Explaining why a suggested change would break compatibility

Review code or pull requests for likely bugs, readability, maintainability, and risks to existing behavior. Supporting scripts and reference checklists help analyze code quality, identify missing tests, and organize findings into a review report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request for bugs and risks to existing behavior
• Checking code readability and maintainability
• Finding test coverage gaps and preparing a review report

Review source files changed during a phase for bugs, security issues, and code quality problems

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.