“receiving”的搜索结果

将代码审查意见与实际代码、支持的运行环境及现有行为进行核对，确认建议是否合理，梳理疑问并依据技术证据回复，再逐项修改和测试。

• 梳理含糊的代码审查意见
• 核实建议修改的兼容性
• 检查拟扩展的功能是否实际使用

帮助启动RuView传感节点，指导构建和烧录ESP32-S3／ESP32-C6固件，配置WiFi与接收地址，检查串口日志，并排查CSI数据未送达的原因。

• 首次配置RuView实体设备
• 重新烧录8 MB和4 MB版本
• 配置WiFi及接收服务器

Process vendor bills from email, PDFs, or photos into proposed accounting entries and a payment plan. Checks duplicates, assigns accounts and jobs, matches purchase and receiving records, and requires separate approval for ledger entries and payments.

中文简介正在准备中。当前显示英语简介。

• Organize accumulated email, PDF, and photographed bills
• Check duplicate invoices and purchase discrepancies
• Assign expenses to accounts and jobs

Receive live Lark/Feishu updates for messages, approvals, tasks, meetings, and more. Stream them as NDJSON, one JSON record per line, with filtering and time or event limits for bots and automated event processing.

中文简介正在准备中。当前显示英语简介。

• Receiving new messages for bot processing
• Monitoring approval and task updates
• Receiving meeting lifecycle and minutes events

Set up Slack alerts for a colony, a group of AI agents, so users can reply when work stalls. The skill prepares the Slack app, stores sending and receiving tokens, connects a channel, and tests notifications.

中文简介正在准备中。当前显示英语简介。

• Receiving Slack alerts when agent work stalls
• Replying from Slack to keep work moving
• Creating a dedicated notification channel

Evaluate code review feedback against the actual code, supported environments, and existing behavior. Clarify uncertain requests, respond with technical evidence, and implement valid changes one at a time with tests for each fix.

中文简介正在准备中。当前显示英语简介。

• Clarifying ambiguous code review comments
• Checking whether suggested changes preserve compatibility
• Assessing whether a requested feature is actually used

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not blind implementation.

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

Verifies review feedback with technical rigor, not blind agreement. Use when receiving review before implementing suggestions.

中文简介正在准备中。当前显示原文说明。

Use when receiving critical feedback on an analysis or manuscript, before implementing suggestions, especially if feedback seems unclear or methodologically questionable - requires verification, not performative agreement or blind changes

中文简介正在准备中。当前显示原文说明。

Process and act on code review feedback. Use when receiving review results.

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

Always use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verification gates (run the command, read the output, then make the claim). Never skip — the cost of false completion claims is higher than the cost of verifying. References: code-review-reception.md, requesting-code-review.md, verification-before-completion.md.

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

中文简介正在准备中。当前显示原文说明。

Triage reviewer comments on a GitHub PR with receiving-code-review discipline — verify each against the codebase, then accept/push-back/clarify, and optionally reply in-thread. Use when responding to received PR feedback. NOT for giving a review (see mk:review-pr); NOT for implementing the fixes (hand off to mk:fix).

中文简介正在准备中。当前显示原文说明。