一键在 Manus 中运行任何 Skill

rt-claw-docs-sync

星标5

分支0

更新时间2026年5月13日 16:42

Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

gevico

gevico/rt-claw

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

rt-claw Docs Sync

Keep documentation accurate and bilingual where the repository already has English and Chinese pairs.

Documentation Map

Path	Purpose
`README.md`	English project overview
`README_zh.md`	Chinese project overview
`docs/en/`	English developer and user documentation
`docs/zh/`	Chinese counterpart documentation
`CLAUDE.md`	Command-level agent reference
`AGENTS.md`	Shared agent instruction source
`.agents/`	Agent-agnostic development skills

Common scopes:

readme: README.md and README_zh.md.
arch: architecture docs and diagrams.
usage: build, run, flash, and shell usage guides.
api: API references and header documentation.
agent: AGENTS.md, CLAUDE.md, GEMINI.md, Copilot instructions, and .agents/.

Workflow

Read the diff and identify changed behavior, APIs, commands, platforms, or configuration.
Update only documentation that the change actually affects.
Preserve EN/ZH parity when changing paired docs.
Keep command examples aligned with Makefile, meson_options.txt, and current scripts.
Do not document unimplemented features as done.
Verify referenced paths and commands exist.
For paired EN/ZH docs, update both sides in the same change unless there is an explicit reason not to.

Change Triggers

claw/services/* -> architecture, usage, and service docs may need updates.
claw/services/tools/* -> Tool Use and usage docs may need updates.
include/* -> API references may need updates.
osal/* -> architecture and porting docs may need updates.
platform/* -> getting-started, usage, and platform docs may need updates.
Makefile, meson_options.txt, or scripts/* -> build and usage docs may need updates.
.agents/*, AGENTS.md, or tool-specific instruction files -> agent guidance needs updates.

Rules

Do not add broad roadmap text for a narrow code change.
Do not change generated files or build artifacts.
Do not create new standalone docs unless the task explicitly asks for them.

同仓库更多 Skills

同仓库

rt-claw-ci-coverage

gevico/rt-claw

Use when adding CI coverage for a new rt-claw module, feature chain, endpoint backend, service integration, or regression.

2026-05-145

rt-claw-build

gevico/rt-claw

Use when building rt-claw, choosing a platform target, running QEMU, flashing hardware, or debugging C/Meson/native build failures.

2026-05-135

rt-claw-code-explorer

gevico/rt-claw

Use when finding rt-claw definitions, call sites, subsystem ownership, build wiring, OSAL boundaries, or platform-specific implementations.

2026-05-135

rt-claw-diagnose

gevico/rt-claw

Use when analyzing rt-claw build logs, QEMU output, serial monitor logs, CI failures, network/API failures, or boot/runtime crashes.

2026-05-135

rt-claw-new-module

gevico/rt-claw

Use when adding a new rt-claw service, driver, tool, platform helper, platform port, or RTOS backend.

2026-05-135

rt-claw-osal-review

gevico/rt-claw

Use when reviewing rt-claw changes for OSAL boundary violations, RTOS coupling, platform leakage, driver layering, or portability risks.

2026-05-135

rt-claw Docs Sync

Keep documentation accurate and bilingual where the repository already has English and Chinese pairs.

Documentation Map

Path

Purpose

README.md

English project overview

README_zh.md

Chinese project overview

docs/en/

English developer and user documentation

docs/zh/

Chinese counterpart documentation

CLAUDE.md

Command-level agent reference

AGENTS.md

Shared agent instruction source

.agents/

Agent-agnostic development skills

Common scopes:

readme: README.md and README_zh.md.

arch: architecture docs and diagrams.

usage: build, run, flash, and shell usage guides.

api: API references and header documentation.

agent: AGENTS.md, CLAUDE.md, GEMINI.md, Copilot instructions, and .agents/.

Workflow

Read the diff and identify changed behavior, APIs, commands, platforms, or configuration.

Update only documentation that the change actually affects.

Preserve EN/ZH parity when changing paired docs.

Keep command examples aligned with Makefile, meson_options.txt, and current scripts.

Do not document unimplemented features as done.

Verify referenced paths and commands exist.

For paired EN/ZH docs, update both sides in the same change unless there is an explicit reason not to.

Change Triggers

claw/services/* -> architecture, usage, and service docs may need updates.

claw/services/tools/* -> Tool Use and usage docs may need updates.

include/* -> API references may need updates.

osal/* -> architecture and porting docs may need updates.

platform/* -> getting-started, usage, and platform docs may need updates.

Makefile, meson_options.txt, or scripts/* -> build and usage docs may need updates.

.agents/*, AGENTS.md, or tool-specific instruction files -> agent guidance needs updates.

Rules

Do not add broad roadmap text for a narrow code change.

Do not change generated files or build artifacts.

Do not create new standalone docs unless the task explicitly asks for them.

name	rt-claw-docs-sync
description	Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization.
license	MIT

name	rt-claw-docs-sync
description	Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization.
license	MIT