「feedback」の検索結果

Azure DevOps pull requests, for repos whose git remote is on dev.azure.com or *.visualstudio.com. Covers comment threads, which `az repos pr` cannot read or post. Use to create a PR for the current branch, check out, list or complete PRs, post code comments on a PR, reply to threads, and assess whether review feedback was addressed. Trigger on "create PR", "checkout PR 123", "list PRs", "complete PR", "comment on the PR", "post these review findings", "check PR feedback", "/dev-azdo:pr".

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

INVOKE THIS SKILL when creating, managing, or using annotation configs on Arize (categorical, continuous, freeform), or applying human annotations to project spans via the Python SDK. Configs are the label schema for human feedback on spans and other surfaces in the Arize UI. Triggers: annotation config, label schema, human feedback schema, bulk annotate spans, update_annotations.

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

Diagnose when intuitive judgment, agent confidence, or expert routing can be trusted by classifying environment validity, feedback quality, and task-boundary fit. Use for confidence calibration, agent routing, expertise audits, and escalation design. NOT for deterministic implementation tasks, pure syntax debugging, or domains with explicit verifiable answers.

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

Diagnose when intuitive judgment, agent confidence, or expert routing can be trusted by classifying environment validity, feedback quality, and task-boundary fit. Use for confidence calibration, agent routing, expertise audits, and escalation design. NOT for deterministic implementation tasks, pure syntax debugging, or domains with explicit verifiable answers.

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

学ぶ目的やこれまでの理解に合わせて、短い対話型レッスンと復習用資料を作るスキル。学習記録を残し、複数回のセッションにわたる学びを支えます。

• 新しい分野を継続して学びたいとき
• クイズとフィードバックで練習
• 復習用の早見表を作りたいとき

論文や研究計画を共通の評価基準で読み、研究方法、根拠、引用、文章構成を点検するスキル。評価の理由と修正の優先順位、次に直す内容を整理します。

• 投稿前の論文を見直したいとき
• 引用が主張を支えるか確認したいとき
• 研究方法と限界を評価したいとき

React / Next.jsのボタン、モーダル、通知、ページ遷移に動きを加え、表示・消去やスクロールに連動するアニメーションを実装するスキル。

• ボタンの操作に動きを付けたいとき
• モーダルや通知の表示・消去
• Next.js App Routerのページ遷移

Webページの表示や操作、APIの応答、ビルド・テストの所要時間を計測するスキル。変更前後の結果を比較し、Gitで共有する基準値をもとに性能の悪化を確認します。

• コード変更前後の性能比較
• ページが遅いという報告の調査
• 公開前に性能目標を確認したいとき

Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)

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

Find progress or deliverables from earlier Paperclip work and add user-requested feedback with human attribution.

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

Iterative design-to-code feedback loop. Critique → adjust → ship cycle for tightening visual fidelity between brief and built UI.

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

Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request.

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

Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation. Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like "review this paper", "analyze this research", "summarize this study", or "write a peer review".

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

Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.

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

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

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

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.

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

Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.

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

Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, timeline, history, clean, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.

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

Agent Media OS for a HyperFrames project. Resolve BGM, SFX, image, icon, brand logo, voice, color grade, or LUT into a frozen local file or paste-ready block + ledger record (one verb, `resolve`); generate via TTS / music / image models when the catalog misses; produce voiceover, transcription, captions, and background removal through one shared audio engine; operate on media (cut / reframe / transform); and reuse assets across projects. Also use for vague feedback that real footage looks dark, flat, boring, should feel retro/camcorder/print/ASCII, needs privacy, or needs a media reveal. When the host app provides its own music or sound-effect tools, use those for music and sound effects; `resolve --type bgm|sfx` needs the heygen CLI. When `HEYGEN_API_BASE` is set, HeyGen calls go through that host with no CLI sign-in.

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

When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups.

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

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit,' 'this sounds like AI,' 'AI slop,' 'de-slop this,' or 'make it sound human.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. Every edit removes AI tells such as 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and sentences that trail into extra comma clauses. For writing new copy, see copywriting.

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

Runs one or more installed review lenses — adversarial critique, edge cases, verification gaps, structure, prose — and reports triaged findings. Use when, and only when, the user asks you to review a diff, a pull request, or an artifact — code or documents, one or many — and actually says "review"; an explicit skill:bmad-review directive from another skill counts as that ask. A request to act on feedback from an earlier review is a change, not a review. Never invoke this uninvited, including on edits you just made.

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

只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitHub 时不得触发，必须改用 cherry-studio-feedback 并默认提交飞书。

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

Use when Cherry Studio 用户希望报告、提交或整理 BUG、UI/UX 问题或功能建议，但未明确要求创建 GitHub Issue。

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