'code-review' 검색 결과

Review code changes through a structured check of requirements, design, correctness, security, performance, and tests. Produce specific, constructive feedback that separates required fixes from optional suggestions, and build shared review guidelines for a development team.

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

• Review a pull request systematically
• Create a shared code review checklist
• Give actionable feedback to junior developers

Review PostgreSQL code for database design, performance, and security issues. Get improvement suggestions covering JSONB, a binary JSON format, arrays, indexes, custom data types, functions, extensions, and rules that control access to individual rows.

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

• Reviewing JSONB and array queries
• Checking table types and constraints
• Improving functions and triggers

Break a large development brief into ordered goals and save plans, progress events, blockers, and evidence in the repository. Coordinate Claude Code sessions through handoff instructions, with final completion requiring cleanup, verification, and code review evidence.

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

• Tracking development work across Claude Code sessions
• Managing ordered goals with attempts and evidence
• Requiring cleanup, verification, and review before completion

Review code changes using a knowledge graph, a map of code relationships, to assess risk and affected behavior. Organize findings by severity, identify missing tests, suggest fixes, and provide a merge recommendation.

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

• Prioritizing review findings by risk
• Checking how changed functions affect other code
• Identifying missing tests and proposing test cases

Investigate bugs using a graph of code relationships. Find relevant functions, trace calls and execution paths, check recent changes, and assess what a proposed fix could affect before reading and changing the implementation.

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

• Narrowing down code related to a bug
• Tracing the execution path that triggers an issue
• Checking whether recent changes caused a bug

Review all changes in a pull request or branch against its base branch. Use a knowledge graph, a map of code relationships, to report affected files and functions, test coverage, API compatibility issues, and recommended actions.

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

• Reviewing all commits in a pull request
• Checking a branch's changes against its base
• Finding callers missed by public API changes

Plan refactoring with dependency analysis, which shows how code parts rely on each other. Find candidates and unreferenced code, preview and apply renames, and compare the resulting impact with the original plan.

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

• Finding refactoring candidates and unreferenced code
• Previewing edits before applying a rename
• Checking affected dependencies and execution paths

Review code changes against the previous commit and identify affected files and functions. Use dependency relationships to assess risk, check missing tests, and produce a focused report with issues and recommendations.

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

• Reviewing changes against the previous commit
• Checking how a change affects other functions
• Finding missing tests for high-risk changes

Have a different AI model review code, analysis, or documents against the original skill's stated requirements. Receive evidence-based findings and a comparison of agreement and disagreement, then decide which recommendations to accept.

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

• Getting a second opinion on substantial code changes
• Reviewing authentication and other security-sensitive changes
• Checking work before a bulk operation

Review code for security vulnerabilities using a checklist covering unsafe input, authentication, access permissions, secrets, and data exposure. Classify findings into four severity levels to distinguish exploitable flaws, issues needing investigation, and smaller improvements.

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

• Review SQL, shell commands, and HTML for unsafe input
• Check authentication and access permissions
• Find exposed credentials and sensitive log data

Reviews pull requests for bugs, error handling, code quality, and style consistency. Organizes feedback into an overview, must-fix issues with file locations, improvement suggestions, and positive notes so reviewers can distinguish urgent problems from refinements.

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

• Finding bugs that must be fixed before merging
• Reviewing TypeScript types and asynchronous code
• Checking naming, imports, and leftover debug statements

Review code for performance bottlenecks across database queries, memory use, frontend rendering, network requests, and algorithms. Use a structured checklist to identify optimization opportunities and classify their severity according to expected load and scale.

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

• Reviewing database queries for avoidable overhead
• Checking memory leaks and unbounded resource growth
• Reviewing React rendering and long-list performance

Turn long Markdown files into a single HTML file for reading, reviewing code, or presenting slides. Routes each input to a specialized converter and applies shared design settings, with navigation and interaction suited to the document type.

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

• Converting long specifications or reports into navigable HTML
• Presenting code reviews with diffs and severity annotations
• Turning Markdown into slides with keyboard navigation

Turn a Markdown code review into a single HTML file with code changes beside severity-labeled comments. Readers can jump to findings, inspect line numbers, and identify the named human reviewer.

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

• Turning a lengthy Markdown code review into HTML
• Reading code changes beside review comments
• Jumping directly to findings by severity

Analyze pull requests and source code across multiple programming languages to identify complexity, security risks, and structural problems. Produce prioritized findings and structured review reports to guide code review decisions.

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

• Prioritizing files for a pull request review
• Finding structural problems in source code
• Checking changes for exposed secrets and injection risks

Implement a planned game development task by gathering its specifications and design decisions, then assigning the right programming specialist. Coordinate source changes, tests where required, visual evidence, and session state for subsequent review and closure.

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

• Implementing a ready game development story
• Assigning implementation to the right programming specialist
• Collecting required tests and visual evidence

Review code changes or a pull request for bugs, effects on existing behavior, test gaps, and project standards. Receive findings supported by the code and a clear account of review coverage, with local fixes available when explicitly requested.

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

• Reviewing a pull request before release
• Checking changes for bugs and test gaps
• Applying review findings locally

Address existing feedback on a GitHub pull request, a proposed code change. Evaluate comments against the code, apply valid fixes, and verify replies and thread resolution, with options for local handoff or resuming saved work.

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

• Addressing feedback across a pull request
• Handling a specific review thread
• Preparing local fixes for someone else to publish

Review a NemoClaw pull request for security risks by examining changed code, configuration, and dependencies. Assess nine categories and report findings with severity, file locations, and recommended fixes, alongside an overall assessment of whether it is safe to merge.

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

• Review a pull request before merging
• Inspect changes linked to an issue
• Check authentication and credential handling

Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.

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

• Review a Handsontable branch or pull request
• Check architecture before or during core changes
• Review keyboard access and performance concerns

Review code for security risks, logic bugs, and performance problems. Receive specific feedback explaining the affected lines or patterns, why they matter, and how to fix them, with required changes separated from optional improvements.

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

• Reviewing code changes before merging a pull request
• Checking input validation, access controls, and secret handling
• Finding inefficient queries and blocking operations

Review GitHub pull requests with specialized agents that check for clear bugs and violations of project instructions in CLAUDE.md. Validate bug findings before posting focused comments on the affected lines, with fix suggestions where appropriate.

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

• Reviewing a pull request for clear bugs
• Checking changes against CLAUDE.md rules
• Posting validated findings on affected lines

Review Doris code changes using project-specific checklists for data correctness, concurrency, memory safety, compatibility, performance, and tests. Trace related code paths and explain findings with concrete failure scenarios, using query plan trees when reviewing optimizer behavior.

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

• Review newly completed Doris code changes
• Check concurrency and memory management in related code paths
• Assess compatibility and test coverage before merging

Review code changes and files for bugs, security risks, performance problems, design issues, and test coverage. Receive a structured report with prioritized findings, concrete improvement examples, positive feedback, and an overall review verdict.

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

• Reviewing a pull request
• Auditing code quality and security
• Finding refactoring opportunities