quick-recap

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Quick Recap

快速回顾

Make completion state obvious at the end of every response.

在每个响应的末尾明确标注完成状态。

Status Block

状态块

Every response that completes a unit of work must end with:

🟢 Actual concise status sentence

Rules:

Keep the status line under 100 characters.
Use
```
🟢
```
when the requested work is finished.
Use
```
🟡
```
when non-routine follow-up remains; name the pending item.
Use
```
🔴
```
only when blocked on user input.
Put the status line at the very end of the response.
Do not add
```
---
```
, spacer lines, or any content after the status line.

每个完成一个工作单元的响应必须以以下内容结尾：

🟢 简洁的实际状态语句

规则：

状态行长度控制在100字符以内。
当请求的工作已完成时，使用
```
🟢
```
。
当存在非常规后续工作时，使用
```
🟡
```
；需指明待处理事项。
仅在等待用户输入而受阻时，使用
```
🔴
```
。
将状态行放在响应的最末尾。
状态行之后不要添加
```
---
```
、分隔线或任何内容。

Installer Behavior

安装器行为

This convention is only automatic when it is present in project or user instructions. When installing this skill, prefer adding the managed

AGENTS.md

CLAUDE.md

block unless the user opts out.

If you are following the convention manually, choose the status from the user's perspective: finished, pending a specific non-routine step, or blocked.

只有当该规范存在于项目或用户说明中时，才会自动生效。安装此skill时，除非用户选择退出，否则优先添加托管的

AGENTS.md

CLAUDE.md

块。

如果手动遵循此规范，请从用户的角度选择状态：已完成、待处理特定非常规步骤，或受阻。

Examples

示例

Finished work:

🟢 Updated quick recap docs with output examples

Non-routine follow-up remains:

🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks

Blocked on user input:

🔴 Need the production API key to continue

已完成工作：

🟢 为快速回顾文档更新了输出示例

存在非常规后续工作：

🟡 代码已更新，测试Webhook前请设置PROVIDER_WEBHOOK_SECRET

等待用户输入受阻：

🔴 需要生产环境API密钥才能继续