「review」の検索結果

Deep Amazon review analysis for competitive intelligence and product improvement. Extract sentiment patterns, recurring complaints, feature requests, and competitive insights from customer feedback. Turn reviews into actionable product development and marketing strategies. Use when the user asks about review analysis, customer feedback, product complaints, sentiment analysis, or what customers think about products.

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

Review generation strategy — Request a Review, follow-up emails, insert cards, Vine, early reviewer programs

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

Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when user asks "review API", "check endpoints", "REST review", or before releasing API changes.

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

Systematic code review for Java with null safety, exception handling, concurrency, and performance checks. Use when user says "review code", "check this PR", "code review", or before merging changes.

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

Plan, triage, and write academic rebuttals and review responses. Use when an AI research agent needs to handle conference, journal, workshop, or grant reviews; classify reviewer concerns; decide what evidence or experiments can change the decision; write an AC-facing executive summary; draft per-reviewer responses; correct factual misunderstandings without sounding hostile; handle novelty, baseline, method, experiment, clarity, and scope objections; or produce a final rebuttal checklist.

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

Review and revise academic papers with a senior-reviewer workflow. Use when an AI research/coding agent needs to work on an existing paper draft, PDF, LaTeX project, Word document, markdown manuscript, rejected paper, or paper idea that already has a concrete direction, and produce: paper maps, weakness audits, insight/novelty checks, reviewer objections, claim-experiment matrices, theory/proof checks, experiment plans, statistics/reproducibility audits, figure/table audits, ethics/compliance checks, revision plans, detailed section edits, or final submission checklists.

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

Code review for the current change, before it is pushed. One command runs the security, secret, dependency and lint scanners that fit the changed files, a separate reviewer that checks every scanner finding and is given every changed line, and prints a short receipt with the path of the full report. Use before every git push, when asked for a code review, a security scan, or to review changes, a diff or a pull request, and when a push was blocked or warned by OpenQodex.

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

Dung khi leader phai DUYET output CHU cua team truoc khi trien khai — content brief co dung insight va dung pillar khong, CTA co ro khong; ads copy va creative co proof cho claim khong, dung tone khong, hook co nam trong 125 ky tu dau khong; verdict Approve / Revise / Redo kem feedback cu the. Kich hoat khi user nhac 'duyet brief', 'review ads copy', 'duyet content', 'check truoc khi chay', 'bai nay dang duoc chua', 'em viet the nay sep xem giup', 'duyet output team'. Khong dung cho — cham diem THIET KE va hinh anh thi dung skill 47-design-review; danh gia nang luc nguoi lam thi dung skill 65-team-performance-review; can nhieu goc nhin phan bien cho mot huong chien luoc thi dung skill 72-hoi-dong-marketing.

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

Use after gsd-code-review has written REVIEW.md, when you want its Critical and Warning findings fixed. Spawns the fixer agent, commits each fix atomically and writes REVIEW-FIX.md (--all, --auto to iterate).

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

Use after a phase's code is written, or when the user asks to review changed files for bugs, security issues, or quality. Spawns the gsd-code-reviewer agent at quick, standard, or deep depth and writes the phase REVIEW.md.

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

Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.

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

Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on team-review.

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

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

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

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

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

Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.

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

Review test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.

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

Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging. This is NOT a general code review.

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

Review code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter. Use this skill when reviewing a small set of changes locally (such as unstaged diff), when dispatched as a sub-task during feature-dev quality review, or when the user wants a critique of a specific file or function.

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

PR size-based review depth, performance review checklist, architecture conformance checks, and framework-specific review patterns.

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

Run a focused STRIDE-based security review using Bug Hunter-native artifacts. Use whenever the user asks for a full security audit, repository security review, weekly security scan, PR security review with deeper validation, or wants dependency CVEs and threat-model context combined into one workflow.

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

Inspect and update NuGet package families using ManagedCode NuGetPackageManager, the nuget-manager CLI, or its VS Code extension. USE FOR: checking outdated packages; dry-run family reviews; applying reviewed literal package and explicit project SDK version updates. DO NOT USE FOR: adding/removing packages; dependency graph resolution; authenticated private-feed setup. INVOKES: inspect declarations, preview and review exact versions, apply authorized changes, then restore and run focused regressions.

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

Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in the browser instead of editing Markdown. Use when a brief or draft needs to go to a client/expert for review, or when building the briefs/index.html entry page for a client folder. The reviewer's input comes back as a JSON file that 04-content-brief Step 9 ingests. Visual quality is delegated to the frontend-design skill.

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

Use when reviewing, designing, or modifying Java enterprise systems that may support EU Market Abuse Regulation concerns, market surveillance, suspicious order and transaction reports, insider dealing controls, unlawful disclosure controls, market manipulation detection, inside information disclosure workflows, insider-list evidence, PDMR transaction notifications, alert explainability, model or rule provenance, reviewer decisions, or compliance escalation. This should trigger for requests such as Review a Java trading surveillance system for MAR controls; Design suspicious order and transaction monitoring evidence; Add alert explainability and reviewer-decision audit trails; Assess AI-assisted market-abuse detection before production release. Part of Plinth Toolkit

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

Runs a product quality review on a journey, feature, landing page, onboarding flow, or AI/agent surface and returns a friction log, a scored critical-journey review, and a taste bar your team can calibrate against. Use when someone asks is this good enough to ship, how polished should it be, why do users bounce, what is our quality bar, how do we build taste, or to review a design, prototype, onboarding, or checkout. Draws on 264 insights from 100 Lenny's Podcast guests incl. Katie Dill, Dylan Field and Stewart Butterfield.

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