docs(zh-CN): sync Chinese docs with latest upstream changes#1308
Open
zdocapp wants to merge 2 commits intoaffaan-m:mainfrom
Open
docs(zh-CN): sync Chinese docs with latest upstream changes#1308zdocapp wants to merge 2 commits intoaffaan-m:mainfrom
zdocapp wants to merge 2 commits intoaffaan-m:mainfrom
Conversation
Contributor
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
Contributor
|
Important Review skippedToo many files! This PR contains 251 files, which is 101 over the limit of 150. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (251)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
37 issues found across 251 files
Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed. We prioritized the most important files first.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="docs/zh-CN/commands/prp-plan.md">
<violation number="1" location="docs/zh-CN/commands/prp-plan.md:126">
P2: Malformed Markdown table: separator row has 4 columns while header/data rows have 3.</violation>
<violation number="2" location="docs/zh-CN/commands/prp-plan.md:482">
P2: Checklist requires build verification, but the command template does not define a corresponding build-validation section.</violation>
</file>
<file name="docs/zh-CN/commands/gan-build.md">
<violation number="1" location="docs/zh-CN/commands/gan-build.md:48">
P2: `--eval-mode` values are inconsistent within the same command doc, mixing canonical tokens with localized labels and creating ambiguous/invalid mode usage.</violation>
<violation number="2" location="docs/zh-CN/commands/gan-build.md:50">
P2: Feedback filename pattern is inconsistent (unpadded `{iteration}` vs zero-padded `001` format), which can break documented workflow expectations.</violation>
</file>
<file name="docs/zh-CN/commands/flutter-review.md">
<violation number="1" location="docs/zh-CN/commands/flutter-review.md:19">
P2: 先决条件缺少团队要求的 CI/自动化检查通过门禁，可能导致在 checks failing/pending 时仍发起评审并被阻断。</violation>
</file>
<file name="docs/zh-CN/agents/opensource-packager.md">
<violation number="1" location="docs/zh-CN/agents/opensource-packager.md:40">
P2: 嵌套代码块示例使用转义反引号而非更长外层 fence，易导致复制后的 Markdown 模板包含错误 fence。</violation>
</file>
<file name="docs/zh-CN/commands/multi-plan.md">
<violation number="1" location="docs/zh-CN/commands/multi-plan.md:219">
P2: The fenced command block was de-indented, so it is no longer nested under the “执行计划” list item and may render as a separate top-level block.</violation>
</file>
<file name="docs/zh-CN/commands/aside.md">
<violation number="1" location="docs/zh-CN/commands/aside.md:82">
P2: Edge-case templates translate protocol labels (`ASIDE`/`WARNING`), making output markers inconsistent within the same command spec.</violation>
</file>
<file name="docs/zh-CN/commands/python-review.md">
<violation number="1" location="docs/zh-CN/commands/python-review.md:318">
P2: Markdown table row is malformed: escaped backticks prevent code span, leaving an unescaped `|` that can break column parsing.</violation>
</file>
<file name="docs/zh-CN/CONTRIBUTING.md">
<violation number="1" location="docs/zh-CN/CONTRIBUTING.md:124">
P2: Nested markdown template blocks use escaped inner backticks under triple outer fences, producing copy-paste-incorrect examples; use longer outer fences instead.</violation>
</file>
<file name="docs/zh-CN/agents/opensource-sanitizer.md">
<violation number="1" location="docs/zh-CN/agents/opensource-sanitizer.md:129">
P2: The Git history scan command can expose full secret values, contradicting the doc’s own rule to never display full secrets.</violation>
</file>
<file name="docs/zh-CN/CODE_OF_CONDUCT.md">
<violation number="1" location="docs/zh-CN/CODE_OF_CONDUCT.md:74">
P2: Escaping brackets broke the intended Markdown reference link, so the attribution text no longer renders as a clickable link.</violation>
</file>
<file name="docs/zh-CN/commands/prp-pr.md">
<violation number="1" location="docs/zh-CN/commands/prp-pr.md:91">
P2: Post-rebase push instruction is inconsistent and likely fails for diverged remote branches; use lease-protected force push.</violation>
<violation number="2" location="docs/zh-CN/commands/prp-pr.md:176">
P2: The doc instructs requesting code review even when CI may still be pending, violating the team’s gate that checks must pass before human review.</violation>
</file>
<file name="docs/zh-CN/commands/code-review.md">
<violation number="1" location="docs/zh-CN/commands/code-review.md:95">
P2: PR 审查流程缺少“冲突即阻断”的明确门禁，且未采集合并状态字段，可能在不可合并 PR 上继续审查。</violation>
<violation number="2" location="docs/zh-CN/commands/code-review.md:110">
P2: PR 审查流程缺少“先确认自动化 checks 通过再开始人工审查”的前置门禁，当前阶段顺序与团队审查要求不一致。</violation>
</file>
<file name="docs/zh-CN/commands/hookify-list.md">
<violation number="1" location="docs/zh-CN/commands/hookify-list.md:18">
P2: 文档流程前后不一致：步骤2读取 `action` 元数据，但步骤3的输出表格未包含对应列，导致 `/hookify-list` 输出契约不明确。</violation>
</file>
<file name="docs/zh-CN/commands/review-pr.md">
<violation number="1" location="docs/zh-CN/commands/review-pr.md:15">
P2: The `/review-pr` workflow omits required readiness gates (green checks and no merge conflicts) before starting review steps, which can trigger invalid or stale reviews.</violation>
<violation number="2" location="docs/zh-CN/commands/review-pr.md:16">
P2: The review workflow incorrectly tells users to use only `gh pr view` for diffs; it should include `gh pr diff` for actual patch content.</violation>
</file>
<file name="docs/zh-CN/commands/e2e.md">
<violation number="1" location="docs/zh-CN/commands/e2e.md:7">
P2: 文档对 `/e2e` 的实现归属存在冲突：前文称委托 `e2e-testing` 技能，后文仍称调用 `e2e-runner` 代理。</violation>
<violation number="2" location="docs/zh-CN/commands/e2e.md:25">
P2: `委托`段落混入未清理的测试代码，破坏了该旧版入口文档应保持的简洁委托语义。</violation>
<violation number="3" location="docs/zh-CN/commands/e2e.md:82">
P2: 多余的四反引号代码围栏把“测试产物/查看产物”整段包进代码块，导致文档结构和渲染错误。</violation>
</file>
<file name="docs/zh-CN/commands/prune.md">
<violation number="1" location="docs/zh-CN/commands/prune.md:28">
P2: Usage comment overstates `/prune` scope and conflicts with the page’s constrained definition of what gets deleted.</violation>
</file>
<file name="docs/zh-CN/commands/orchestrate.md">
<violation number="1" location="docs/zh-CN/commands/orchestrate.md:44">
P2: Misplaced 4-backtick fence breaks Markdown structure and causes the `并行执行` section to render as code instead of normal documentation.</violation>
</file>
<file name="docs/zh-CN/README.md">
<violation number="1" location="docs/zh-CN/README.md:1">
P2: Language-switcher links in zh-CN README over-traverse (`../../../` / `../../../../`), likely breaking locale and English navigation.</violation>
<violation number="2" location="docs/zh-CN/README.md:1426">
P2: User-facing docs newly link to an unvetted external repository, violating project supply-chain trust guidance.</violation>
</file>
<file name="docs/zh-CN/commands/go-review.md">
<violation number="1" location="docs/zh-CN/commands/go-review.md:134">
P2: Localized `失败：` replaces canonical `FAIL:` status token in the go-review example, creating inconsistent status-token format within the same command doc.</violation>
</file>
<file name="docs/zh-CN/commands/prp-commit.md">
<violation number="1" location="docs/zh-CN/commands/prp-commit.md:36">
P2: `only new files` uses whitespace-unsafe `xargs git add`, which breaks on untracked filenames containing spaces/newlines.</violation>
</file>
<file name="docs/zh-CN/commands/go-build.md">
<violation number="1" location="docs/zh-CN/commands/go-build.md:142">
P2: Localized status token (`通过`) in example output is inconsistent with standardized `PASS`/`SUCCESS` style tokens used across resolver docs, reducing output-to-log fidelity.</violation>
</file>
<file name="docs/zh-CN/agents/gan-evaluator.md">
<violation number="1" location="docs/zh-CN/agents/gan-evaluator.md:45">
P2: Playwright execution instructions are inconsistent with declared tools and include invalid CLI command usage (`playwright navigate`), risking evaluator workflow failure.</violation>
</file>
<file name="docs/zh-CN/commands/harness-audit.md">
<violation number="1" location="docs/zh-CN/commands/harness-audit.md:7">
P2: `--root` was added to command usage but omitted from the `$ARGUMENTS` block, causing inconsistent argument documentation.</violation>
</file>
<file name="docs/zh-CN/commands/learn-eval.md">
<violation number="1" location="docs/zh-CN/commands/learn-eval.md:86">
P2: Step 6 sub-bullets were de-indented to top level, which can break/obscure ordered-list nesting in rendered Markdown.</violation>
</file>
<file name="docs/zh-CN/commands/instinct-import.md">
<violation number="1" location="docs/zh-CN/commands/instinct-import.md:47">
P2: Localized zh-CN documentation regressed to English in the import-process example block, reducing translation consistency and reader usability.</violation>
</file>
<file name="docs/zh-CN/agents/dart-build-resolver.md">
<violation number="1" location="docs/zh-CN/agents/dart-build-resolver.md:45">
P2: 文档对纯 Dart 项目与工作流要求不一致：前文允许 `dart analyze`，后文却强制每次都运行 `flutter analyze`。</violation>
<violation number="2" location="docs/zh-CN/agents/dart-build-resolver.md:66">
P2: Troubleshooting guidance incorrectly claims `--delete-conflicting-outputs` can force rebuild when build_runner reports no actions were run.</violation>
</file>
<file name="docs/zh-CN/agents/csharp-reviewer.md">
<violation number="1" location="docs/zh-CN/agents/csharp-reviewer.md:13">
P2: Reviewer instructions do not enforce the required gate that automated checks must pass before starting code review.</violation>
<violation number="2" location="docs/zh-CN/agents/csharp-reviewer.md:15">
P2: C# reviewer prompt lacks a merge-conflict/merge-readiness gate before beginning review, contrary to team review policy.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.
| 将发现结果编译成单一参考： | ||
|
|
||
| | 类别 | 文件:行号 | 模式 | 关键代码片段 | | ||
| |---|---|---|---| |
Contributor
There was a problem hiding this comment.
P2: Malformed Markdown table: separator row has 4 columns while header/data rows have 3.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/commands/prp-plan.md, line 126:
<comment>Malformed Markdown table: separator row has 4 columns while header/data rows have 3.</comment>
<file context>
@@ -0,0 +1,499 @@
+将发现结果编译成单一参考：
+
+| 类别 | 文件:行号 | 模式 | 关键代码片段 |
+|---|---|---|---|
+| 命名 | `src/services/userService.ts:1-5` | 驼峰式服务，帕斯卡式类型 | `export class UserService` |
+| 错误 | `src/middleware/errorHandler.ts:10-25` | 自定义 AppError 类 | `throw new AppError(...)` |
</file context>
Suggested change
| |---|---|---|---| | |
| |---|---|---| |
| ### 验证覆盖范围 | ||
| - [ ] 静态分析命令已指定 | ||
| - [ ] 测试命令已指定 | ||
| - [ ] 构建验证已包含 |
Contributor
There was a problem hiding this comment.
P2: Checklist requires build verification, but the command template does not define a corresponding build-validation section.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/commands/prp-plan.md, line 482:
<comment>Checklist requires build verification, but the command template does not define a corresponding build-validation section.</comment>
<file context>
@@ -0,0 +1,499 @@
+### 验证覆盖范围
+- [ ] 静态分析命令已指定
+- [ ] 测试命令已指定
+- [ ] 构建验证已包含
+
+### UX 清晰度
</file context>
| - 读取 eval-rubric.md 和 spec.md | ||
| - 测试实时应用程序（模式：playwright/截图/仅代码） | ||
| - 根据评分标准打分 | ||
| - 将反馈写入 feedback/feedback-{iteration}.md |
Contributor
There was a problem hiding this comment.
P2: Feedback filename pattern is inconsistent (unpadded {iteration} vs zero-padded 001 format), which can break documented workflow expectations.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/commands/gan-build.md, line 50:
<comment>Feedback filename pattern is inconsistent (unpadded `{iteration}` vs zero-padded `001` format), which can break documented workflow expectations.</comment>
<file context>
@@ -0,0 +1,105 @@
+ - 读取 eval-rubric.md 和 spec.md
+ - 测试实时应用程序（模式：playwright/截图/仅代码）
+ - 根据评分标准打分
+ - 将反馈写入 feedback/feedback-{iteration}.md
+
+ # 等待评估器完成
</file context>
| # 评估 | ||
| 通过 Task 工具启动 gan-evaluator 代理： | ||
| - 读取 eval-rubric.md 和 spec.md | ||
| - 测试实时应用程序（模式：playwright/截图/仅代码） |
Contributor
There was a problem hiding this comment.
P2: --eval-mode values are inconsistent within the same command doc, mixing canonical tokens with localized labels and creating ambiguous/invalid mode usage.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/commands/gan-build.md, line 48:
<comment>`--eval-mode` values are inconsistent within the same command doc, mixing canonical tokens with localized labels and creating ambiguous/invalid mode usage.</comment>
<file context>
@@ -0,0 +1,105 @@
+ # 评估
+ 通过 Task 工具启动 gan-evaluator 代理：
+ - 读取 eval-rubric.md 和 spec.md
+ - 测试实时应用程序（模式：playwright/截图/仅代码）
+ - 根据评分标准打分
+ - 将反馈写入 feedback/feedback-{iteration}.md
</file context>
|
|
||
| ## 先决条件 | ||
|
|
||
| 在运行 `/flutter-review` 之前，请确保： |
Contributor
There was a problem hiding this comment.
P2: 先决条件缺少团队要求的 CI/自动化检查通过门禁，可能导致在 checks failing/pending 时仍发起评审并被阻断。
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/commands/flutter-review.md, line 19:
<comment>先决条件缺少团队要求的 CI/自动化检查通过门禁，可能导致在 checks failing/pending 时仍发起评审并被阻断。</comment>
<file context>
@@ -0,0 +1,118 @@
+
+## 先决条件
+
+在运行 `/flutter-review` 之前，请确保：
+
+1. **构建通过** — 先运行 `/flutter-build`；对无法构建的代码进行审查是不完整的
</file context>
|
|
||
| ``` | ||
| 从 team-instincts.yaml 导入本能 | ||
| Importing instincts from: team-instincts.yaml |
Contributor
There was a problem hiding this comment.
P2: Localized zh-CN documentation regressed to English in the import-process example block, reducing translation consistency and reader usability.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/commands/instinct-import.md, line 47:
<comment>Localized zh-CN documentation regressed to English in the import-process example block, reducing translation consistency and reader usability.</comment>
<file context>
@@ -44,33 +44,33 @@ python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <
- 从 team-instincts.yaml 导入本能
- Importing instincts from: team-instincts.yaml
================================================
</file context>
</details>
<a href="https://www.cubic.dev/action/fix/violation/62012417-a35b-4b43-961e-0e551c7c8a45" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="https://cubic.dev/buttons/fix-with-cubic-light.svg">
<img alt="Fix with Cubic" src="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
</picture>
</a>
| | `The class 'X' doesn't implement 'Y'` | 缺少 `implements` 或缺少方法 | 添加方法或修正类签名 | | ||
| | `Because X depends on Y >=A and Z depends on Y <B, version solving failed` | Pub 版本冲突 | 调整版本约束或添加 `dependency_overrides` | | ||
| | `Could not find a file named "pubspec.yaml"` | 工作目录错误 | 从项目根目录运行 | | ||
| | `build_runner: No actions were run` | build\_runner 输入无变化 | 使用 `--delete-conflicting-outputs` 强制重新构建 | |
Contributor
There was a problem hiding this comment.
P2: Troubleshooting guidance incorrectly claims --delete-conflicting-outputs can force rebuild when build_runner reports no actions were run.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/agents/dart-build-resolver.md, line 66:
<comment>Troubleshooting guidance incorrectly claims `--delete-conflicting-outputs` can force rebuild when build_runner reports no actions were run.</comment>
<file context>
@@ -0,0 +1,202 @@
+| `The class 'X' doesn't implement 'Y'` | 缺少 `implements` 或缺少方法 | 添加方法或修正类签名 |
+| `Because X depends on Y >=A and Z depends on Y <B, version solving failed` | Pub 版本冲突 | 调整版本约束或添加 `dependency_overrides` |
+| `Could not find a file named "pubspec.yaml"` | 工作目录错误 | 从项目根目录运行 |
+| `build_runner: No actions were run` | build\_runner 输入无变化 | 使用 `--delete-conflicting-outputs` 强制重新构建 |
+| `Part of directive found, but 'X' expected` | 生成的文件过时 | 删除 `.g.dart` 文件并重新运行 build\_runner |
+
</file context>
| @@ -0,0 +1,202 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
P2: 文档对纯 Dart 项目与工作流要求不一致：前文允许 dart analyze，后文却强制每次都运行 flutter analyze。
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/agents/dart-build-resolver.md, line 45:
<comment>文档对纯 Dart 项目与工作流要求不一致：前文允许 `dart analyze`，后文却强制每次都运行 `flutter analyze`。</comment>
<file context>
@@ -0,0 +1,202 @@
+## 解决工作流
+
+```text
+1. flutter analyze -> 解析错误信息
+2. Read affected file -> 理解上下文
+3. Apply minimal fix -> 仅应用必要修复
</file context>
| 1. 运行 `git diff -- '*.cs'` 以查看最近的 C# 文件更改 | ||
| 2. 如果可用，运行 `dotnet build` 和 `dotnet format --verify-no-changes` | ||
| 3. 重点关注修改过的 `.cs` 文件 | ||
| 4. 立即开始审查 |
Contributor
There was a problem hiding this comment.
P2: C# reviewer prompt lacks a merge-conflict/merge-readiness gate before beginning review, contrary to team review policy.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/agents/csharp-reviewer.md, line 15:
<comment>C# reviewer prompt lacks a merge-conflict/merge-readiness gate before beginning review, contrary to team review policy.</comment>
<file context>
@@ -0,0 +1,109 @@
+1. 运行 `git diff -- '*.cs'` 以查看最近的 C# 文件更改
+2. 如果可用，运行 `dotnet build` 和 `dotnet format --verify-no-changes`
+3. 重点关注修改过的 `.cs` 文件
+4. 立即开始审查
+
+## 审查优先级
</file context>
| 当被调用时： | ||
|
|
||
| 1. 运行 `git diff -- '*.cs'` 以查看最近的 C# 文件更改 | ||
| 2. 如果可用，运行 `dotnet build` 和 `dotnet format --verify-no-changes` |
Contributor
There was a problem hiding this comment.
P2: Reviewer instructions do not enforce the required gate that automated checks must pass before starting code review.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/zh-CN/agents/csharp-reviewer.md, line 13:
<comment>Reviewer instructions do not enforce the required gate that automated checks must pass before starting code review.</comment>
<file context>
@@ -0,0 +1,109 @@
+当被调用时：
+
+1. 运行 `git diff -- '*.cs'` 以查看最近的 C# 文件更改
+2. 如果可用，运行 `dotnet build` 和 `dotnet format --verify-no-changes`
+3. 重点关注修改过的 `.cs` 文件
+4. 立即开始审查
</file context>
Contributor
Author
|
The CI tests are failing, but I’m not yet sure if it’s the same issue as observed locally. When running tests locally on the latest npm run testI get 5 failing tests, but the failure output differs from what is shown in CI. Local test output: So at the moment, it's unclear whether:
Any guidance on how to align the environments or interpret the CI failures would be appreciated. |
Contributor
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
This PR performs an incremental zh-CN translation sync based on the latest commit from main(62519f2).
Approach
Notes / Trade-offs
Why This Change
#1218 (comment)
Testing Done
node tests/run-all.js)Type of Change
fix:Bug fixfeat:New featurerefactor:Code refactoringdocs:Documentationtest:Testschore:Maintenance/toolingci:CI/CD changesSecurity & Quality Checklist
Documentation
Summary by cubic
Synced zh-CN docs to upstream 1.10.0 (commit 62519f2), adding new content and aligning command/agent docs with current workflows and ECC 2.0 alpha. Also fixed the language selector links and several translations in
docs/zh-CN/README.mdand related pages.New Features
/code-reviewwith PR mode; introduced/review-pr.prp-plan,prp-implement,prp-commit,prp-pr,prp-prd.gan-build,gan-design) plusgan-*agents.dart-build-resolver,flutter-reviewer; new Dart rules (coding style, testing, security, hooks).performance-optimizer,seo-specialist,comment-analyzer,silent-failure-hunter,type-design-analyzer, open‑source pipeline agents, and more.hookify,hookify-list,hookify-configure,hookify-help) and updated hooks guide.ecc2/, repository assessment/evaluation docs, and updated zh-CNREADME.mdandCHANGELOG.md.Migration
documentation-lookup,tdd-workflow,context-budget,claude-devfleet).~/.claude/session-data/; update any scripts or usage that assumed~/.claude/sessions/(reading from old path is still supported)./review-pror run/code-reviewwith a PR number/URL.cargo build --manifest-path ecc2/Cargo.tomland useecc-tuicommands as documented.Written for commit 28c7c55. Summary will update on new commits.