openpress-collaborate

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

OpenPress Collaborate

OpenPress 协作技能

This skill selects how an agent and user review authored-content changes. The Agent GUI carries instructions; Workbench renders Current and Proposed pages and collects Proposal feedback.

该技能用于确定Agent与用户审查已创作内容变更的方式。Agent GUI承载指令；Workbench渲染当前页面与提议页面，并收集提议反馈。

Choose A Mode

选择模式

Mode	Trigger	Source mutation
Answer	analysis or review without a requested change	none
Propose	non-trivial edit, preview, or writing judgment	review handoff only
Apply	explicit request to apply the current Preview	exact reviewed replacements
Direct	explicit review bypass, or a small mechanical edit	direct source edit

Initial creation belongs to the format skill because new files have no useful

before

text. Use Propose for later revision.

模式	触发条件	源文件变更
Answer	无需变更请求的分析或审查	无
Propose	非琐碎编辑、预览或写作判断	仅移交审查内容
Apply	明确要求套用当前预览内容	完全按审查后的内容替换
Direct	明确跳过审查，或小型机械性编辑	直接编辑源文件

初始内容创建属于格式技能范畴，因为新文件没有可用的

before

文本。后续修订请使用Propose模式。

Propose

Propose模式

Read current source, workspace instructions, relevant writing/format skills, and related pending
```
@openpress-comment
```
markers.
Do not edit authored
```
press/
```
source.
Replace
```
.openpress/review/current.json
```
with the complete current proposal set:

json

{
  "proposals": [
    {
      "path": "press/book/chapters/intro.mdx",
      "before": "Exact current source text.",
      "after": "Exact replacement text.",
      "note": "Short reason for this change"
    }
  ]
}

Each Proposal must target authored

.mdx

.tsx

under

press/

, use a non-empty exact unique

before

, contain the complete

after

replacement, and include one plain-language

note

. For insertion, include stable neighboring text in both values. Use an empty

after

for deletion. Order by path and source position.

Write only

path

before

after

, and

note

; Workbench may add

feedback

. Replace the whole handoff each pass—do not preserve ids, history, hashes, or superseded feedback.

Tell the user to open Changes in Workbench. Current and Proposed markers share the same note and feedback. Stop before editing source.

读取当前源代码、工作区指令、相关写作/格式技能以及待处理的
```
@openpress-comment
```
标记。
请勿编辑
```
press/
```
目录下的已创作源文件。
将
```
.openpress/review/current.json
```
替换为完整的当前提议集合：

json

{
  "proposals": [
    {
      "path": "press/book/chapters/intro.mdx",
      "before": "Exact current source text.",
      "after": "Exact replacement text.",
      "note": "Short reason for this change"
    }
  ]
}

每个提议必须针对

press/

目录下的

.mdx

或

.tsx

已创作文件，使用非空且唯一的精确

before

文本，包含完整的

after

替换内容，并附上一段通俗易懂的

note

说明。如需插入内容，请在

before

和

after

中包含稳定的相邻文本。如需删除内容，将

after

设为空。按文件路径和源文件位置排序。

仅编写

path

、

before

、

after

和

note

字段；Workbench可能会添加

feedback

字段。每次迭代都替换整个移交内容——请勿保留ID、历史记录、哈希值或已过时的反馈。

告知用户在Workbench中打开Changes页面。当前标记与提议标记共享相同的说明和反馈信息。在编辑源文件前停止操作。

Refresh From Feedback

根据反馈刷新内容

Read the current handoff before replacing it. Treat

accept

reject

more-info

, and free-text feedback as input, re-read current source, reconsider the complete change set, then write a fresh proposal file without copying old feedback.

在替换移交内容前，请先读取当前的移交内容。将

accept

、

reject

、

more-info

以及自由文本反馈作为输入，重新读取当前源代码，重新考虑完整的变更集合，然后编写新的提议文件，不要复制旧的反馈内容。

Apply

Apply模式

Apply only after an explicit instruction such as「套用目前 Preview」or「開始修改」.

Read the handoff and every target file fresh.
If any Proposal has
```
reject
```
or
```
more-info
```
, refresh or answer instead.
Before changing any file, verify every
```
before
```
occurs exactly once. If any is missing or ambiguous, change nothing.
Apply every replacement exactly; add no unreviewed wording.
Remove only
```
@openpress-comment
```
markers actually satisfied by the applied change.
Delete the handoff after all edits succeed.
Follow
```
openpress
```
→ Review And Delivery Gate when visual or delivery readiness is part of the request.

Never partially apply a Preview.

仅在收到明确指令（如「套用目前 Preview」或「開始修改」）后才执行套用操作。

重新读取移交内容和所有目标文件。
如果任何提议包含
```
reject
```
或
```
more-info
```
状态，请改为刷新内容或回复用户。
在修改任何文件前，验证每个
```
before
```
文本在文件中恰好出现一次。如果任何
```
before
```
文本缺失或存在歧义，则不进行任何修改。
严格按照每个替换内容执行操作；不得添加未经过审查的内容。
仅移除已应用变更实际满足的
```
@openpress-comment
```
标记。
所有编辑成功完成后，删除移交内容。
如果请求包含视觉验证或交付就绪要求，请遵循
```
openpress
```
→ Review And Delivery Gate流程。

绝不要部分套用预览内容。

Direct

Direct模式

Follow the owning format skill and normal OpenPress source boundary. For comment markers, use

openpress-apply-comments

. Use the shared review gate when the result must be visually verified or delivered.

When editing prose with semantic figure/table references:

Preserve existing
```
fig-*
```
and
```
tbl-*
```
target IDs unless the requested change requires renaming the target.
Cite targets with
```
@fig-stable-name
```
and
```
@tbl-stable-name
```
; never rewrite resolved labels such as
```
圖 2
```
or
```
表 3
```
into source.
When adding, removing, moving, or renaming a captioned target, inspect and update all matching mentions in the same proposal or direct edit.
For React figures, verify the stable ID reaches the root
```
<figure>
```
; for Markdown tables, keep it on the immediately preceding
```
<TableCaption id="tbl-...">
```
.
After applying the change, build the Press so missing, duplicate, malformed, or cross-kind targets fail before delivery, then click a representative cross-page reference in Workbench.

遵循所属格式技能和常规OpenPress源文件边界规则。对于评论标记，请使用

openpress-apply-comments

工具。如果结果需要视觉验证或交付，请使用共享审查流程。

编辑包含语义化图表/表格引用的文本时：

保留现有的
```
fig-*
```
和
```
tbl-*
```
目标ID，除非请求的变更要求重命名目标。
使用
```
@fig-stable-name
```
和
```
@tbl-stable-name
```
引用目标；切勿将已解析的标签（如
```
圖 2
```
或
```
表 3
```
）重写到源文件中。
添加、删除、移动或重命名带标题的目标时，请检查并更新同一提议或直接编辑中的所有匹配引用。
对于React图表，请验证稳定ID是否传递到根
```
<figure>
```
组件；对于Markdown表格，请将稳定ID保留在紧邻的
```
<TableCaption id="tbl-...">
```
组件上。
应用变更后，构建Press以确保缺失、重复、格式错误或跨类型的目标在交付前暴露问题，然后在Workbench中点击一个具有代表性的跨页面引用进行验证。

Safety

安全规则

```
openpress
```
owns CLI lifecycle and source/generated boundaries.
Format and writing skills own content judgment.
```
openpress-apply-comments
```
owns marker mechanics.
Never publish; route publishing to
```
openpress-deploy
```
.

```
openpress
```
负责CLI生命周期以及源文件/生成文件的边界管理。
格式和写作技能负责内容判断。
```
openpress-apply-comments
```
负责标记机制。
绝不要直接发布；请将发布操作交由
```
openpress-deploy
```
处理。