1.5万 件 ・ 関連度順
概要と使いどころ
Set up systematic review monitoring across e-commerce platforms. Track new reviews, detect negative review spikes, monitor competitor reviews, and automate review response workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Run all four review skills (investor, customer, operator, skeptic) on a business plan in sequence, then auto-decide where verdicts agree and surface only disagreements + taste decisions to the user. One command = full review gauntlet, intelligently filtered. Use when a plan is ready to be stress-tested before commit. Triggered by: 'panel review', 'review panel', 'run all reviews', 'review gauntlet', '审议会', '四方评审'.
日本語の概要は準備中です。原文の説明を表示しています。
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous multi-pass editor for law review articles, student notes, seminar papers and other legal scholarship. Runs six specialized passes — structure, substantive critique, Bluebook citations, grammar and clarity, fact-checking against sources, and a synthesizing memo — and delivers an editorial memo with issues prioritized as critical, substantial or minor and keyed to specific footnotes and paragraphs. Handles articles of any length, including 50,000-word pieces, by chunking on section boundaries. Reads .docx directly. Use when editing, critiquing, workshopping or pre-submission-reviewing academic legal writing. Triggers on "edit my article," "review this draft," "critique my note," "check my Bluebook citations," "is my argument sound," "read my law review piece," "workshop this paper," "pre-submission review." Chunking needs Python 3; fact-checking needs web search; both degrade gracefully without.
日本語の概要は準備中です。原文の説明を表示しています。
Contract intelligence and contract operations workflow skill for Claude and Codex. Guides the full contract lifecycle review process from intake and playbook normalization through clause review, deviation scoring, negotiation planning, approval routing, QA, and action recommendations. Reviews legal, business, operational, compliance, privacy, security, technology, and AI-related risks across contracts and legal documents. Supports NDAs, SaaS agreements, DPAs, procurement contracts, commercial agreements, contract comparisons, redlines, approval packages, clause research, and drafting. Warning-Comprehensive reviews can consume significant Claude/OpenAI tokens, especially for large agreements, playbooks, exhibits, schedules, and multi-document reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch Google review ratings and review counts for businesses via DataForSEO API. Use when the user asks to check Google reviews, get review counts, compare business ratings, audit Google Maps presence, or analyze competitor reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Mines a pull request's review threads for lessons that generalize beyond that PR, reconstructs each against the actual code before deciding, checks whether it is already codified, and routes the genuinely-new, durable ones into Infrahub's internal documentation — `dev/knowledge/`, `dev/guides/`, `dev/guidelines/`, the `AGENTS.md` files, and `.agents/rules/` — proposing edits first and applying only with the user's approval. TRIGGER when: the user wants to turn PR review feedback into durable conventions, guidelines, or rules; capture recurring reviewer comments as internal documentation; or check whether review lessons are reflected in the knowledge/guides/guidelines/AGENTS.md/rules layer. DO NOT TRIGGER when: sweeping a feature's changes for documentation coverage across all layers → use `audit-docs`; extracting knowledge from completed spec directories → `speckit-opsmill-extract`; only replying to or resolving review threads → normal git/gh flow.
日本語の概要は準備中です。原文の説明を表示しています。
Previews and exports documents stored in Volcengine TOS: generate PDF/PNG/JPG previews, read page counts, resolve HTML preview URLs, and batch-export PDF pages as images. Use this skill when the user needs to convert or preview office documents (Word, Excel, PPT, PDF), export specific pages as images, get document page counts, or generate HTML preview links — even if they don't explicitly mention 'doc-preview' or 'document conversion'.
日本語の概要は準備中です。原文の説明を表示しています。
Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining. Use when user wants to commit changes, get a second-opinion code review from Codex, push changes, create a PR, check PR status, fix review comments, clean up branches after merge, or mine tribal knowledge from PR reviews. Use for "commit my changes", "codex review", "push my changes", "create a PR", "pr status", "fix PR comments", "clean up branches", "mine PRs", or "address feedback".
日本語の概要は準備中です。原文の説明を表示しています。
Run an independent peer review via Claude. Use when the user asks to "peer review", "peer review my code", "peer review my plan", "get a second opinion", or "independent review".
日本語の概要は準備中です。原文の説明を表示しています。
Run an independent peer review via Codex. Use when the user asks to "peer review", "peer review my code", "peer review my plan", "get a second opinion", or "independent review".
日本語の概要は準備中です。原文の説明を表示しています。
Use for social science academic paper drafting, outlining, diagnosis, review, and revision. Trigger for topic diagnosis, research question refinement, literature review planning, CNKI/Google Scholar literature search-to-Zotero workflows, structured paper reading notes, theoretical framework design, research design critique, draft review, section or paragraph revision, citation and evidence risk checking, causal-claim checking, and pre-submission review. Do not use for purely creative writing or non-academic editing.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failure_scenario) and want them published on a PR as inline review comments. Triggers include "post these review comments on the PR", "associate comments to files in the PR", "publish review findings to PR
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing someone else's manuscript for a journal, such as after a review invitation or for a revised R1/R2 version. Drafts a structured, constructive review in the journal's format. Never for your own manuscript; that is /self-review.
日本語の概要は準備中です。原文の説明を表示しています。
Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect, evaluate, or check code, even if they never use the word "review." Does not post comments to GitHub pull requests — use post-code-review-to-pr for that. Does not analyze architectural structure or module boundaries — use architectural-analysis for that. Does not explain code or a PR to build understanding before reviewing — use code-overview for a written overview, or code-walkthrough to be paced through it one step at a time. Does not map bounded contexts or domain boundaries — use ddd-analysis for that. Does not capture feedback on Han's own skills — use han-feedback for that.
日本語の概要は準備中です。原文の説明を表示しています。
Run a full pull request review and post review comments directly to the current branch's GitHub PR. Requires the gh CLI to be installed and a PR to already exist for the current branch. Use when you want review feedback posted to GitHub as PR comments. For local code review without posting to GitHub, use code-review instead. Does not write or update PR descriptions — use update-pr-description for that.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a PR description from the current branch's changes against a GitHub PR, using the gh CLI. Use when writing, drafting, or updating pull request descriptions, PR summaries, or PR bodies. Does not review code or post review comments — use code-review for local review or post-code-review-to-pr for posting a review to GitHub.
日本語の概要は準備中です。原文の説明を表示しています。
Deep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (conventions, cross-references) is skill-validate's job — this skill finds gaps that would realistically surface when someone actually uses the skill: missing scenario handling, ambiguous instructions, silent failure cases, and behavioral inconsistencies. Filters out theoretical edge cases, low-likelihood speculation, and findings owned by other skills. Use after writing or significantly changing any skill, or when the user says 'review this skill', 'deep review', 'does this skill work', 'find gaps in this skill', 'stress test this skill', 'review from different angles', or 'skill review'. Standalone — does not call other skills.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a structured code review by composing validation checklists from relevant atoms based on what code changed. Loads atoms conditionally -- clean-code always, architecture/DDD/security/tests only when the delta touches their domain. Produces a severity-ordered report with specific locations and fixes. Use when the user asks to 'review this', 'code review', 'quality check', 'validate the code', 'check my code', 'review the delta', or 'review this PR'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes for correctness, security, performance, and code quality. Use when the user asks to review a diff, review code changes, review commits, or perform a code review. Input can be: (1) a text diff pasted directly, (2) one or more git commit hashes to extract the diff from, or (3) a git range like abc123..def456. The user may also provide task description or requirements that motivated the change.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive sales and revenue operations skill. Use when building a sales team, doing founder-led sales, hiring first sales reps, navigating enterprise deals, implementing product-led sales, designing sales compensation plans, defining ICP, mapping buyer personas, or optimizing the revenue engine (RevOps). Activates for: sales strategy, rev ops, revenue operations, sales enablement, sales compensation, ICP, ideal customer profile, buyer persona, sales process, deal execution, lead scoring, lead routing, lead lifecycle, MQL, SQL, pipeline management, CRM automation, sales qualification, BANT, MEDDIC, founder sales, enterprise sales, product-led sales, startup sales, SDR, AE, quota, ramp, commission plan.
日本語の概要は準備中です。原文の説明を表示しています。