1.2천건 · 관련도순
Collect customer reviews for a Taobao or Tmall product using its item ID. Extract reviewer names, dates, purchased variants, review text, and photo URLs across review pages to prepare material for feedback analysis or review datasets.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare three or four ways to frame a talk, with strengths, weaknesses, and audience fit. Generate titles, conference proposal descriptions, and a peer feedback draft, then confirm the chosen direction before scripting.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a pull request for merging by sorting review feedback, applying fixes in batches, and checking automated tests and review status. Product, architecture, and scope decisions are brought to the user for a choice.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Handle pull request review feedback by collecting comments, grouping requests, planning fixes, and validating changes before replying. The workflow covers team members and trusted GitHub automation, with individual replies and resolution of addressed discussion threads.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn existing pull request review comments into prioritized next steps by checking them against the current code. Separate outstanding concerns, addressed feedback, and questions needing replies, then implement and validate fixes when requested.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Configure a software delivery workflow that turns selected feedback and maintenance signals into verified, reviewed changes. Define information sources, schedules, working directories, and separate permissions for actions such as implementation, merging, deployment, and notifications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Look across feedback, operational data, errors, and delivery failures over a defined period to find recurring problems. Trace patterns to shared causes, examine earlier fixes, and recommend systemic changes, implementing and verifying them only when configured policies allow.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Collect product feedback, usage data, runtime errors, and issue reports from configured sources. Classify and group findings with supporting evidence, then apply separate project rules for implementing fixes, requesting clarification, or closing reports.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Send feedback to the Nexu team. Use when the user says /feedback followed by their message.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "triage launch feedback", "cluster reviews, comments, and board posts into themes", or "set up a you asked, we shipped loop"; produces a feedback theme digest (frequency, severity, representative quotes per theme), an open→planned→started→completed/declined status loop with duplicate-merge and notification rules, shipped-change announcement material, and a compliant social-proof harvest protocol (never incentivized store reviews). Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager. 反馈分诊/状态环/社证收割/评测合规
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates an in-app feedback collection form with category selection, text input, optional screenshot attachment, device diagnostics, and smart routing — directing happy users to App Store reviews and unhappy users to support. Use when user wants feedback, bug reports, feature requests, or contact support forms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used only when the user explicitly asks to use `$ralph-specum-feedback`, or explicitly asks Ralph Specum in Codex to draft or submit feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes you a ready-to-use script for a feedback or hard conversation, then rehearses the pushback. Use when you need to give tough feedback, confront a peer, tell a report they are underperforming, deny a promotion, prepare to fire someone, say no to your boss, ask for feedback, or repair a conversation that went badly. Draws on 66 Lenny's Podcast guests including Kim Scott, Carole Robin and Alisa Cohn.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback to GitHub. Does not assess architectural health or structural risk — use architectural-analysis for architectural concerns. Does not research open-ended options, prior art, or how something works when nothing is broken — use research for that. Does not plan the structural change a root cause calls for — use plan-a-change. Does not map bounded contexts or domain boundaries — use ddd-analysis. Does not capture feedback on Han's own skills — use han-feedback for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture structured feedback on the Han skills and agents used in the current session and optionally post it as a GitHub issue to testdouble/han. Use at the end of any session where one or more han-* skills or agents ran, to rate a run, log what worked and what didn't, or submit observations for maintainers. Does not review code, investigate bugs, or research options; use code-review, investigate, or research for those. Does not provide feedback on skills or agents from non-Han plugins.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents performance management appropriately.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze NPS, CSAT, and qualitative customer feedback to extract themes, identify trends, and generate actionable insight reports. Use when the user requests customer feedback analysis or provides relevant inputs for this workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Collect and manage product feedback with Canny. Use when a user asks to set up a feature request board, prioritize product feedback, build a public roadmap, or let users vote on features.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The craft of producing creative assets that communicate brand, product, and message effectively. Creative communications bridges strategy and execution—translating brand positioning and marketing goals into visual, audio, and interactive experiences that resonate with audiences. This skill covers creative briefing, creative production workflows, asset creation, creative feedback, and cross-channel creative adaptation. Great creative communications amplifies strategy; it doesn't replace it. Use when "creative, creative brief, assets, video, motion, animation, creative production, photoshoot, visual content, creative review, ad creative, creative feedback, creative, production, video, motion, assets, briefs, feedback, visual-content" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in the human side of code review. Covers giving feedback that lands, receiving criticism gracefully, navigating disagreements, and building a healthy review culture. Understands that code review is as much about relationships as it is about code quality. Use when "code review, PR feedback, review comments, how to give feedback, harsh review, review culture, constructive criticism, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.