'rev' 검색 결과

Turn previously fetched pull request reviews into an ordered action plan. Separate distinct findings, track deferred work in Linear, validate that every triage decision is complete, and produce JSON and Markdown files for the implementation phase.

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

• Planning responses to fetched PR review feedback
• Separating multiple findings within a single review
• Tracking deferred review work in Linear

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

Review pull requests at a specific commit using existing discussions, review plans, and executed checks. Produce a detailed Chinese review and a concise English verdict, then publish and read back the result to confirm its contents.

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

• Review a named pull request at a specific commit
• Review a queue filtered by state or time period
• Audit changes against maintainer guidance

Collect Google Maps reviews through BrowserAct using search keywords, language, and country settings. Retrieve reviewer names, ratings, review text, dates, and likes as structured data for reputation research, competitor comparisons, and customer feedback analysis.

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

• Collect reviews for nearby shops and facilities
• Track feedback for a brand location
• Gather competitor reviews for comparison

Draft, audit, or revise responses to reviewers for Nature-family journals. Links each reviewer concern to manuscript evidence or a documented change, and identifies unanswered comments, missing author input, and issues that need resolution before submission.

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

• Drafting responses for major or minor manuscript revisions
• Checking a response draft for unanswered reviewer comments
• Linking responses to manuscript changes

Review changes since the last npm release through parallel change analysis, hands-on quality checks, and an overall release assessment. Receive a readiness verdict, blocking issues, version recommendations, and a draft changelog with compatibility concerns.

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

• Assess readiness before an npm release
• Check breaking changes and migration needs
• Review version bump recommendations

Iteratively improve research by having Claude Code review code, results, and drafts while Codex implements fixes. Repeat until the assessment meets the stopping criteria or the round limit is reached, preserving feedback and unresolved issues.

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

• Repeating research reviews and fixes before submission
• Checking whether claims match code and experiment results
• Tracking how reviewer concerns are addressed across rounds

Review a pull request using repository checks, verified code references, and current official documentation. Assess correctness, security, structure, and unnecessary code, then post one consolidated GitHub review with inline findings and an evidence-based verdict.

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

• Review a pull request before merging
• Check code structure and unnecessary comments
• Verify dependency changes against official documentation

Produce honest product reviews and buying guides without fabricated first-hand experience, using disclosed evidence tiers: verified specs, owner-experience synthesis at scale, expert triangulation, and hands-on only when true. Use this skill whenever the user wants to write product reviews or buying guides without hands-on access, set up a review methodology, add evidence disclosure to review content, align reviews with Google's reviews system or FTC affiliate disclosure expectations, or decide when Review and Product schema are honest to use. Triggers on product review, buying guide, best-of list, review methodology, evidence basis, hands-on testing, we tested, affiliate review site, review disclosure, methodology block, original research, reviews system. Also triggers when review content claims testing that did not happen, or when an affiliate site needs a trust mechanism that survives scrutiny.

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

Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the user asks to 'review and address in a loop', 'iterate review until approved', 'auto review-and-fix this PR', 'loop /ocr:review and /ocr:address', or to take a changeset all the way to a clean APPROVE with the default reviewer team. Wraps the /ocr:review (.ocr/commands/review.md) and /ocr:address (.ocr/commands/address.md) skills; needs a feature branch with an open GitHub PR and the gh CLI for posting.

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

공유된 OpenClaw 검토 절차와 보조 스크립트로 코드를 확인하고, 대상 저장소의 고유 요구 사항도 적용합니다. 실제 검토 절차는 공통 설치본을 참조합니다.

• 공통 절차로 코드를 검토할 때
• 저장소별 검토 요구 사항을 확인할 때
• 공유 검토 절차를 한곳에서 갱신할 때

Review code changes with several independent reviewers working in parallel, then receive organized findings. Request a quick or thorough review, choose to hand off fixes, or run without interaction when another workflow or CI job initiates the review.

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

• Review code changes from multiple independent perspectives
• Choose a quick or thorough review
• Receive findings with fixes handed off

Review Git changes with the ocr command-line tool and a configured AI model. Get line-level findings grouped by severity for working changes, commits, or branch comparisons, with code fixes applied when explicitly requested.

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

• Reviewing changes before a commit
• Checking a pull request or branch comparison
• Inspecting a specific commit for issues

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

Plan revenue growth for B2B SaaS businesses by analyzing sales opportunities, pricing, customer retention, and sales capacity. Develop scenario forecasts, churn intervention plans, hiring models, and revenue reporting for board discussions.

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

• Forecast next quarter’s revenue
• Analyze churn and expansion revenue
• Review pricing and packaging

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

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 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

Create a literature review from a topic, journals, and publication period. Multiple agents search academic databases, collect available PDFs and citation records, organize findings by theme, and draft, review, revise, and compile a LaTeX document.

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

• Review research on a topic across several journals
• Organize recent papers by shared themes
• Collect open-access PDFs and BibTeX references

Coordinate research, drafting, citation and data verification, AI review, revision, and final formatting through connected skills. Start from a research topic, an existing manuscript, or reviewer comments, with progress tracking and user checkpoints.

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

• Manage a paper from initial research to final formatting
• Begin verification and review from an existing draft
• Organize reviewer comments and prepare revisions

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.

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