'viewer' 검색 결과

Draft, diagnose, and improve IEEE rebuttals, revision plans, cover letters, response letters, and point-by-point replies using routed reviewer-comment handling. Use when responding to IEEE reviewer or editor comments about novelty, scope, method, experiments, baselines, figures, tables, citations, writing, LaTeX formatting, limitations, compliance, technical correctness, or reviewer comments that appear generic, contradictory, unsupported, careless, or possibly AI-generated.

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

Review IEEE conference, journal, Transactions, Letters, or magazine manuscripts from a technical reviewer perspective using routed IEEE review gates. Use when evaluating scope fit, novelty, validity, data, clarity, compliance, advancement, engineering significance, method soundness, experiment sufficiency, baseline fairness, figure/table quality, formatting risks, rejection risk, major revision strategy, pre-submission readiness, or the quality and specificity of reviewer comments that may be generic, careless, contradictory, or possibly AI-generated.

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

Address PR reviewer feedback by evaluating comments, proposing fixes, and executing after user approval. Use when the user wants to handle review comments on an existing PR, address PR feedback, fix PR comments, respond to reviewer suggestions, or process code review feedback. Triggers on "address PR feedback", "handle review comments", "fix PR comments", "respond to PR review", "process reviewer feedback", or when given a PR number/URL with intent to address its comments.

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

Ensure site/viewer/lib has correct symlinks to src/viewer/assets/lib

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

Create a custom JavaScript viewer extending DG.JsViewer with properties and rendering

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

Nature-style atmospheric science manuscript reviewer skill for testing observation, reanalysis, model, aerosol-cloud-radiation, extreme-event, circulation-mechanism and attribution claims against their physical evidence chain.

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

Nature-style engineering manuscript reviewer skill for testing devices, robots, platforms, systems, algorithms embodied in physical systems and engineering methods against requirements, validation, benchmarking, uncertainty, robustness and failure modes.

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

Nature-style climate and ecology manuscript reviewer skill for testing biodiversity, ecosystem-function, carbon-cycle, conservation, global-change and ecological-inference claims against sampling, causal design, model structure, uncertainty and management scope.

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

Nature-style materials science manuscript reviewer skill for testing materials design, synthesis, processing, structure-property, mechanism, stability, scalability, computational prediction and application claims against materials evidence chains.

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

Nature-style chemistry manuscript reviewer skill for testing synthesis, catalysis, chemical biology, molecular/materials chemistry and analytical claims against identity, purity, controls, selectivity, mechanism, scope, reproducibility and quantitative comparison.

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

Nature-style remote-sensing manuscript reviewer skill for evaluating Earth-observation products, retrievals, machine-learning maps, validation design, uncertainty propagation, spatial transferability and claim-scope calibration.

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

Nature-style hydrology manuscript reviewer skill for testing streamflow, runoff, groundwater, water storage, drought, flood, hydroclimate and water-resource claims against water-balance closure, hydrologic signatures, model structure and observational constraints.

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

AI-PLC Registry ビューア（ブラウザ）の起動・停止。experimental/registry-viewer を手でコピーしたときだけ使える。

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

AI-PLCの Registry ビューア（ブラウザで Project 一覧・詳細・食い違い・起動プロンプトを見る）を起動・停止する。「Registryビューア開いて」「AI-PLCのプロジェクトを画面で見たい」で使う。experimental/registry-viewer を手でコピーしたときだけ使える。

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

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.

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

Use when the user asks for a code review by a fleet of specialized reviewer agents, wants multiple independent reviewer perspectives, or asks to run reviewers in single-pass or iterative fix-until-clean mode. Launches focused subagents for correctness, security, architecture, conventions, simplicity, UX, reliability, telemetry, testing, compatibility, and documentation review.

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

Before committing any non-trivial change, dispatch the diff to a reviewer runtime via ATO (`ato dispatch <reviewer> --session <id>`), parse the numbered/severity-tagged findings, apply or defer each one with a recorded justification, then commit. Fights the "build passes therefore ship it" failure mode — what Garry Tan calls the AI agent complexity ratchet. Place in the v2.16 stack: this skill is the LAST gate. `ato-warroom` decides the design; `ato-mission` runs the multi-step work and produces the diff; `ato-review` checks the diff before commit. When the review is part of a Mission, dispatch the review with `--require-tools read_file,grep,git_diff,git_log` so the reviewer can walk the source itself instead of reasoning from a paraphrase (PR-1.5 tool surface). Receipts land in `execution_logs` and the Mission narrative. Fires automatically before commits touching public surface (CLI subcommands, Tauri commands, MCP tools, schema migrations, security boundaries) or whenever a diff exceeds ~50 LOC of behavior change.

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

Use when recording, tallying, or triaging stochastic review findings — the append-only JSONL ledger where Tier 2 (advisory, unevidenced) reviewer output goes instead of blocking language. Triggers on "log this finding", "ledger add", "tally the findings", "triage findings", "is this finding recurring", "retire this noise", or whenever a reviewer produces an unevidenced concern that should be measured for recurrence rather than chased. For the review itself see code-review-and-quality or skill-library-review; for verifying formal claims with deterministic evidence see adversarial-claims-reviewer.

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

Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.

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

Read-only reviewer for agent-flow. Judges one diff against the acceptance criteria, AGENTS.md rules, protected paths and risk boundaries; returns a JSON verdict with line-anchored findings. Use when launched with AGENT_FLOW_ROLE=reviewer or asked for an agent-flow review of a diff.

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

Inspect GitHub PR for CI failures, merge conflicts, update-branch requirements, reviewer comments, change requests, and unresolved review threads. Create fix plans and implement after user approval. Reply to ALL reviewer comments with action taken or reason for not addressing, then resolve threads. Notify reviewers after fixes.

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

Reviews a proposal, business case, deck or plan in character as a Chief Operating Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific sections, delivery and operational risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a COO review", "pressure-test the delivery plan", "what would our COO say about this", "check the timeline and capacity" or "find the execution gaps before the steering committee". Do not use for financial questions, use cfo-reviewer instead; for architecture or vendor questions, use cto-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Data Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, data and AI governance risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CDO review", "pressure-test the data governance in this plan", "what would a CDO say about this", "check the metric definitions and data sources" or "prepare this for the data governance board". Do not use for security controls or third-party security risk, use ciso-reviewer instead; for contract, liability or regulatory terms, use general-counsel-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific passages, marketing risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CMO review", "pressure-test the positioning", "what would a CMO say about this", "challenge the launch plan" or "check the messaging and audience". Do not use for price economics, margins or payback, use cfo-reviewer instead; for sales pipeline mechanics, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.

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