「rev」の検索結果

Review a data analysis for quality, correctness, and reproducibility. Covers data quality assessment, assumption checking, model validation, data leakage detection, and reproducibility verification. Use when reviewing a colleague's analysis before publication, validating an ML pipeline before production deployment, auditing a report for regulatory or business decision-making, or performing a second-analyst review in a regulated environment.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect one bounded Proto UI pull-request slice, produce canonical review input, and route each eligible exact head toward review and integration. Use for review queues, linked work, evidence gaps, merge conflicts, stale revisions, or portfolio health. This evidence leaf is read-only; authorized review and integration continue in their registered leaves.

日本語の概要は準備中です。原文の説明を表示しています。

Apply one exact-target reversible Proto UI Issue, pull-request, review-thread, or Actions collaboration update and return a verified receipt. Use for governed title/body or label repair, update-branch, ready-for-review, review requests, fixed-thread resolution, bounded status comments, and exact-run CI recheck. Do not submit a review disposition, merge, close, publish, release, or change privileged repository settings.

日本語の概要は準備中です。原文の説明を表示しています。

Designer's eye plan review — interactive, like CEO and Eng review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. For live site visual audits, use /design-review. Use when asked to "review the design plan" or "design critique".

日本語の概要は準備中です。原文の説明を表示しています。

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff".

日本語の概要は準備中です。原文の説明を表示しています。

Review or polish a product UI for accessibility, brand fidelity, hierarchy, rhythm, responsive behavior, themes, interaction states, and generic AI-template patterns. Use for visual audits, accessibility checks, UX polish, UI critique, or pre-ship design review. Do not use for generic code review, backend review, or API design.

日本語の概要は準備中です。原文の説明を表示しています。

`.agent/agents/reviewer.md` を入口に、PR差分やローカル差分を日本語でレビューするスキル。ユーザーが「レビュー」「PR確認」「差分確認」「コードレビュー」「reviewer」「レビュー指摘に対応」などを依頼したときに使う。GitHubレビュー指摘の対応（分類・方針提示・Worker委譲・resolved化）も扱う。

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

日本語の概要は準備中です。原文の説明を表示しています。

Perform critical Rust code reviews covering correctness, edition 2024 compliance, error handling, API design, async pitfalls, and dependency hygiene. ALWAYS use this skill when the user wants to review, audit, or critically evaluate Rust code — whether that's a PR diff, a specific crate or module, a cross-cutting concern like error handling, or the whole codebase. This includes requests to "review my changes", "check this code", "audit for best practices", "look for issues", "what's wrong with this", or "flag anything that could bite us". Use it even when the user doesn't say "review" explicitly but is asking you to find problems, inconsistencies, or anti-patterns in existing Rust code. Do NOT use for requests to write, fix, refactor, test, explain, or implement code — only for evaluating existing code.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive code review checklist and methodology. Use when reviewing PRs, conducting code audits, or assessing code quality. Keywords: review, PR, code review, audit, assess, quality, check

日本語の概要は準備中です。原文の説明を表示しています。

Performs a white-box security review of Atlassian Forge apps using structured, Forge-specific security rules and evidence-driven reporting. Use when the user asks for a Forge security review, security audit, vuln assessment, pentest-style code review, authz review, tenant isolation analysis, web trigger hardening, or static analysis execution for a Forge app.

日本語の概要は準備中です。原文の説明を表示しています。

Use this agent when you need to systematically review existing GO annotations for a gene and make curation decisions based on literature evidence and functional analysis. This agent should be called after seeding the SPECIES/GENE/GENE-ai-review.yaml file, which seeds each annotation with `action: PENDING`; these should all be manually reviewed.

日本語の概要は準備中です。原文の説明を表示しています。

Review computational protein or gene function predictions and fill PredictionReview YAML files using the COR/CNN/LSP/UNC/PLI/NPI/REP biological-validity taxonomy. Use for ProtNLM, DeepECTF, BioReason/GO-GPT, InterPro2GO, PANTHER/IBA, CLEAN, GloEC, MAPred, ProteinInfer, or other predicted EC/GO annotations, including audits of the evidence and reasoning in existing prediction reviews.

日本語の概要は準備中です。原文の説明を表示しています。

Use this agent when you need to synthesize and distill the core functions of a gene from multiple information sources (textual summaries, reviewed annotations, bioinformatics analysis) and populate the `core_functions` section of a gene review YAML file. This agent should be called after completing the gene research, annotation review, and bioinformatics analysis phases of a gene review project.

日本語の概要は準備中です。原文の説明を表示しています。

Full legal plugin suite for commercial contract review, privacy/DPA analysis, and AI governance vendor reviews. Use when the user invokes /commercial-legal:review, /privacy-legal:dpa-review, /ai-governance-legal:vendor-ai-review, renewal tracking, DSAR responses, or EU AI Act triage.

日本語の概要は準備中です。原文の説明を表示しています。

Review a PR or the current branch for a Lumen design-system change — routes each changed file to React (web/Tailwind) or React Native (useStyleSheet) guidelines, checks the Nx version plan, and reports a flat, severity-scored finding list. Use when the user asks to review a PR, review code changes, check a branch, do a local code review, or provides a GitHub PR URL.

日本語の概要は準備中です。原文の説明を表示しています。

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

日本語の概要は準備中です。原文の説明を表示しています。

Phase 3 of the feature-pipeline suite. Run this after /fp-implement has pushed all commits and printed the M2 stop hook. Spawns a sandboxed sub-agent (HEAVIER) in an isolated worktree to run RED/GREEN tests against the PR diff and post a structured review comment. Use when you need an independent agent to verify correctness of implementation changes before CI runs — especially for schema mutations, CLI surface changes, or doc-touching commits. Triggers on: "review the PR", "run sandbox review", "fp-review", "Phase 3", "check the implementation", "validate the changes", "run tests on the PR", or any instruction to verify what /fp-implement just pushed.

日本語の概要は準備中です。原文の説明を表示しています。

Close out a review/meta branch that lands an evidence-ingest / curation batch: create the named nodes, ingest verified evidence, appraise Trust Magnitude, calibrate stars, wire suites, correct upstream naming, stage ONLY the intended artifacts (dropping CRLF churn and blocking leaks), validate, and open the PR. Use when a curation/ingest batch is verified and ready to land, or when the user says "close the review/meta branch", "land the ingest batch", "wrap up the intake PR", "/gaia-review-meta-close". Wraps the deterministic hygiene in scripts/review_meta_close.py and gates the judgment calls (calibration, Origin, suite promotion, naming, merge) behind explicit human checkpoints.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants their way of working with Claude assessed — "review my session", "how am I using Claude Code", "audit my setup / workflow", "am I following best practices", "coach me", "what should I improve" — or pastes a Claude.ai/Cowork/Tag transcript and asks how they could have worked better. Do NOT use for reviewing code changes (that is code review) or for teaching a product from scratch (use academy-learn); this skill only reviews how the human works with Claude.

日本語の概要は準備中です。原文の説明を表示しています。

Sweep a PR's automated + human review comments and act on them — especially for material (large / logic-bearing) PRs. Handles "sweep the PR comments", "check PR review feedback", "address review comments", "did the bots flag anything", and the pre-/post-merge review pass on any non-trivial PR.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews game audio code for Wwise/FMOD integration safety, custom DSP plugin correctness, and audio middleware usage. Use when the user asks to review a Wwise plugin, check an FMOD DSP effect, audit game audio middleware integration, or asks "is my game audio code safe?". Trigger on phrases like "review my Wwise plugin", "check FMOD DSP effect", "is my game audio code safe", "review my audio middleware integration", or when you see AkPluginInfo, FMOD_DSP_DESCRIPTION, IMetaSoundSource, or Execute/process callbacks in game audio code.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews audio DSP code for numerical correctness. Use when the user asks to review, audit, or check DSP code for correctness issues — filters, feedback loops, fixed-point arithmetic, accumulation loops, or any numeric computation in audio code. Trigger on "check this filter for NaN", "why does my reverb blow up?", "is this numerically stable?", "why do I hear DC in my output?". Pairs with audio-dsp-review (realtime safety); this skill covers numeric correctness. Flag issues proactively.

日本語の概要は準備中です。原文の説明を表示しています。

Revenue Intelligence setup: activating the RI app and its CRM Analytics assets, Einstein deal insights, the opportunity-change waterfall, and forecast-accuracy analytics for sales leaders. NOT for configuring the Pipeline Inspection view, its metrics and review cadence - use admin/pipeline-review-design. NOT for forecast types, categories, rollups and quotas - use admin/collaborative-forecasts.

日本語の概要は準備中です。原文の説明を表示しています。