'review' 검색 결과

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

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

• Reviewing a pull request before merging
• Getting a second opinion on AI-written code
• Checking authentication or data access code

Run Polly AI Review and Open Code Review repeatedly on a pull request. Track each finding, fix relevant issues, document justified dismissals, and verify that review evidence and recorded decisions cover the latest commit.

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

• Resolving findings from two automated PR reviewers
• Reviewing each new commit after fixes
• Recording evidence for dismissed or duplicate findings

Review medium to large code changes using checks selected for the actual patch. Analyze the change and surrounding code, assign focused reviews by function, file, or feature, and combine findings with locations, confidence levels, and supporting evidence.

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

• Reviewing patches of roughly 50 to 1,000 lines
• Checking risks specific to a changed feature
• Reviewing changes alongside callers and related implementations

Extract the same fields from a batch of contracts or other documents into a comparison spreadsheet. Each answer includes a source quote and location, while missing, ambiguous, and review-required information is clearly distinguished for human verification.

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

• Compare contract clauses during M&A due diligence
• Audit vendor contracts using a shared set of fields
• Review dates and notice periods across a lease portfolio

Review code using shared OpenClaw instructions and a Python helper, while also following the target repository’s review requirements. This skill points to a common installation that supplies the actual review procedure.

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

• Reviewing code with shared OpenClaw instructions
• Applying repository-specific review requirements
• Keeping shared review instructions up to date

Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, and Socratic guided modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review.

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

Review code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps and low-value tests by running internal reviews and a peer review in parallel and returning combined findings. Single-concern with a type argument, or full review with no argument. Use when the user asks to "review my code", "full code review", "review my changes", "check for bugs", "scan for bugs", "review correctness", "security audit", "find vulnerabilities", "review security", "check API usage", "verify against docs", "check for cross-file duplication", "review consistency", "check for code reuse", "review simplicity", "find untested code", "find redundant tests", or "review test coverage".

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

Drive a GitHub Copilot (or any bot reviewer) pull-request review to a clean pass without babysitting it: fix each finding in its own commit, reply to the review thread with the fix sha, resolve the thread, re-request the bot, and poll for the async re-review. Covers the thread node-id (PRRT_...) vs comment databaseId distinction, the resolveReviewThread GraphQL mutation, the copilot-pull-request-reviewer[bot] slug, and how to read the bot's verdict (COMMENTED plus a "human review recommended" banner is not a blocking finding). Use when Copilot has left review comments on your PR, when bot review threads must be closed out with an auditable fix-reply-resolve trail before merge, or when you need to verify that a re-review actually landed on the new HEAD rather than the old one.

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

Simulate a Nature-style reviewer assessment from the referee perspective rather than an author rebuttal. Use when the user wants a pre-submission review, reviewer report, peer-review style critique, novelty/significance/technical soundness assessment, reviewer-style manuscript evaluation, 审稿人视角评估, 预审稿意见, or Nature reviewer report. Return 3 reviewer reports plus a cross-review synthesis, grounded only in the local Nature reviewer source basis. Also trigger on general pre-submission review requests during academic writing even without the word "Nature", such as getting a mock peer review for any journal, critiquing a draft as a reviewer would, assessing novelty/rigor before submission, and Chinese phrasings like 审稿人视角、模拟审稿、预审、帮我审一下论文、投稿前自审、审稿意见模拟、找论文问题.

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

review-all を実行し、指摘内容をコードに反映、bun run c / bun run lint / bun test で自己検証し、CONVERGED/NOT_CONVERGED の収束判定付き完了レポートを /tmp/arima-review-fix-result.md に出力する。レビュー→修正→検証→レポートを一気通貫で行うスキル。スコープ引数は /review-all と同じ（wt / PR #N / vs:<branch> / range / ファイル列挙）。review-fix-loop からの自動呼び出し（mode=non-interactive）にも対応。Use when user says 'レビューして直して', 'review and fix', '自動修正', 'レビュー反映', or when invoked by review-fix-loop.

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

Review a GitNexus pull request for production readiness with seven coordinated reviewer agents. Combine their findings and have a final critic check the draft, producing a review without editing code or posting results.

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

• Reviewing a GitNexus pull request before production use
• Combining findings from multiple reviewer agents
• Checking a review draft before finalizing it

Coordinate GitHub pull request reviews by assigning comment triage and code changes to dedicated sub-agents. Repeat the process, track decisions and progress, and reply to and resolve threads as fixes are completed.

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

• Work through outstanding pull request review comments
• Separate required fixes from items outside the pull request scope
• Repeat review and implementation until actionable items are cleared

Collect and validate the review state of a GitHub pull request, then generate a readable Markdown report, a text summary, and a list of items to address before review triage begins.

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

• Collecting the current review state of a pull request
• Summarizing unresolved threads and review comments
• Preparing review items for subsequent triage

Improve research through repeated Gemini reviews, code changes, experiments, and analysis. The workflow records full feedback and actions, then stops when both the score and readiness criteria are met or the round limit is reached.

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

• Improving research through repeated external reviews
• Implementing and checking fixes for research weaknesses
• Keeping a complete record of reviews and experiments

Ask external AI command-line tools to independently review a development phase plan. Collect feedback by reviewer in REVIEWS.md, then feed the results into GSD planning to support revisions.

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

• Getting independent AI reviews before implementation
• Comparing feedback from multiple AI reviewers
• Saving structured review feedback in a document

Review development plans with external AI tools, then revise and review them again while actionable concerns remain. Choose reviewers and a cycle limit to work toward a plan with resolved review findings.

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

• Review a development plan before implementation
• Revise plans using feedback from multiple AI reviewers
• Use a local model server to review plans

Write Chinese code review feedback that clearly distinguishes required fixes, suggestions, and optional advice. Use question and suggestion templates, organize review summaries, and follow guidance for mixed Chinese-English comments and commit messages.

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

• Writing Chinese review comments with clear priorities
• Rephrasing blunt feedback as questions or suggestions
• Standardizing Chinese-English comments and commit messages

Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C#/.NET, Kotlin, Swift, Dart, Flutter, NestJS, C/C++, Zig, CSS/Less/Sass, Qt, and more. Covers architecture review, performance review, security audit, code quality anti-patterns, and common bugs across all ecosystems. Use when: reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, performance reviews, checking code quality, finding bugs, giving feedback on code.

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

Monitor PR review comments and automatically classify and address reviewer feedback including code changes, questions, and nits. Use when handling PR reviews, addressing reviewer comments, responding to code review feedback, or automating review resolution. Triggers on handle reviews, PR review, address feedback, reviewer comments, code review, review response.

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

Let the host AI agent review Git changes while ocr selects files and resolves review rules. Receive findings grouped by severity, plus coverage details showing which files were reviewed or skipped and why.

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

• Reviewing changes with the current AI agent
• Checking branch differences or a single commit
• Reviewing files against their applicable rules

Draft self-assessments, peer reviews, and feedback for managers using concrete examples of work and collaboration. Organizes achievements around context, actions, and results, matches your writing voice, and flags sections that need more evidence or detail.

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

• Prepare an annual or mid-year self-assessment
• Draft a peer review with specific examples
• Write constructive feedback for a manager

Review completed code changes against the original requirements, choosing review depth by behavioral risk. Coordinate independent reviewers, resolve actionable findings, and verify that the delivered changes match the content actually reviewed.

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

• Review completed changes before final verification
• Choose review depth based on behavioral risk
• Re-review fixes after actionable findings

Review a GitLab merge request linked to a Factory work item, verify the current commit, and publish findings with a test report. It records the review verdict on the card and prepares a session handoff without merging.

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

• Review a GitLab merge request assigned through Factory
• Verify earlier review findings against the current commit
• Publish test results and an evidence-based verdict

Create disposable OpenWork previews for hands-on review of app and Den changes. Choose local, Daytona, or Freestyle environments as supported, reopen existing previews, update supported frontend changes while preserving progress, and reset or stop environments when finished.

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

• Trying OpenWork changes before merging a PR
• Reviewing signup and team administration flows
• Testing the desktop app together with Den