「feedback」の検索結果

Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.

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

Use for feedback and feature requests to the Muse team. Whenever your response tells the user you can't do a specific thing they wanted, or accepts them giving up on one, offer once to file feedback in that response. This covers missing integrations you can't do yourself, capabilities you lack, and tasks that keep failing at a specific point. File only on their go-ahead. Also use when asked to send, view, check, or withdraw feedback.

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

Collect and submit feedback about Superset (bug reports, feature requests, or general feedback) privately to the Superset team or as a public GitHub issue. Use when the user wants to report a Superset bug, request a feature, or send feedback about Superset.

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

Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.

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

Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.

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

Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".

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

Interpret third-party feedback by running parallel internal and peer interpretations to surface intent, correctness concerns, and ambiguities. Use when the user asks to "interpret feedback", "interpret comments", "what does this feedback mean", "clarify reviewer intent", "understand this review", or "interpret these suggestions".

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

Prepare a user-reviewed Arch Studio bug report or feature request for GitHub. Use when the user runs /as:studio-feedback, says "report a bug", "this skill broke", "send feedback", or requests a feature. Do not use for Claude Code's native /feedback command.

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

Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).

Design of active analog circuits built around operational amplifiers and discrete gain stages — inverting, non-inverting, difference, and instrumentation topologies, negative feedback and loop stability (gain-bandwidth product, phase margin, compensation), active filters (Sallen-Key, multiple-feedback biquad), sinusoidal and relaxation oscillators, comparators and Schmitt triggers, voltage references (bandgap, shunt, series), and linear versus switching voltage regulators. Covers how to pick a topology, close a feedback loop that stays stable, set gain and bandwidth, and choose a power-conversion approach. Use when designing an amplifier, filter, oscillator, reference, comparator, or regulator, or when reasoning about feedback stability, loop gain, phase margin, or op-amp non-idealities.

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

Customer feedback analysis — sentiment detection, NPS/CSAT frameworks, feature request clustering, support ticket triage, churn signal detection, and feedback-to-roadmap translation

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

Inject juice and game feel into gameplay code using the project's chosen middleware. Use when adding screen shake, tweens, particles, audio feedback, haptics, hitstop, or any form of "juice" to gameplay events. Triggers on requests like "add juice", "make this feel better", "add screen shake", "polish this feature", "add feedback to this action", "make the hit feel impactful", "add particles when", "screen shake on damage", "tween this", "add camera shake", "make this snappy", or any game feel, polish, or feedback work. Always reads ProjectConfig.yaml -> feel_tools and docs/GFD.md Feedback Matrix before generating code.

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

Help users draft and, when authorized, submit feedback to volcengine/volcengine-skills: skill problems, missing capabilities, cloud scenarios, and successful Agent workflows. Use for explicit feedback or sharing requests, or an optional invitation at a natural summary after Volcengine CLI errors or an incompletely solved task. Feedback never blocks the main task.

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

Deliver feedback using Kim Scott's Radical Candor framework - care personally while challenging directly. Use when a leader needs to give difficult feedback, says "I need to tell someone something hard", "how do I give feedback without hurting them", "I've been avoiding a conversation", "my direct report isn't performing", "someone on my team has a blind spot", "I keep sugarcoating things", or "how do I be honest without being a jerk". Also trigger when someone describes being too nice (ruinous empathy) or too harsh (obnoxious aggression), or when they describe avoiding a conversation they know they need to have.

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

Use for feedback and feature requests to the Muse team. Whenever your response tells the user you can't do a specific thing they wanted, or accepts them giving up on one, offer once to file feedback in that response. This covers missing integrations you can't do yourself, capabilities you lack, and tasks that keep failing at a specific point. File only on their go-ahead. Also use when asked to send, view, check, or withdraw feedback.

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

Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.

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

Identifies when task outputs require iteration based on quality signals, unmet requirements, or explicit feedback. Triggers appropriate re-execution strategies. Activate on 'needs iteration', 'retry needed', 'not good enough', 'try again', 'refine output'. NOT for feedback generation (use dag-feedback-synthesizer) or convergence tracking (use dag-convergence-monitor).

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

Address GitHub PR review comments at line, file, and PR level by fetching, evaluating, fixing, committing, and resolving feedback. Use when invoked as `$pr-resolve-review-feedback` or when the user asks to resolve PR feedback.

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

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

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

Identifies when task outputs require iteration based on quality signals, unmet requirements, or explicit feedback. Triggers appropriate re-execution strategies. Activate on 'needs iteration', 'retry needed', 'not good enough', 'try again', 'refine output'. NOT for feedback generation (use dag-feedback-synthesizer) or convergence tracking (use dag-convergence-monitor).

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

OpenClawのリリース候補を人が試すために、隔離コピーなどの検証環境を準備し、テストの進行とフィードバック整理を支援します。公開前の報告確認も扱います。

• Gatewayの隔離コピーで検証したいとき
• 操作画面ごとに人がテストしたいとき
• 公開前に検証報告を確認したいとき

OpenClaw Control UIの画面変更を、状態別の比較ギャラリーと実ブラウザの操作テストで確認し、利用者のコメントや変更前後の画像を残すスキル。

• 読み込み・空・エラー状態の比較
• 画面変更への意見を集めたいとき
• 模擬Gatewayでチャット操作を検証

コードレビューの指摘を実際のコードや対応環境と照らし合わせ、妥当性を確認します。不明点の整理、根拠を示した返答、修正ごとのテストまで進めるスキルです。

• 曖昧なレビュー指摘を整理したいとき
• 提案された変更の互換性確認
• 追加機能が使われているか調べたいとき

360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.

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